1. Insert Frame
2. Anchor it "as Character"
3. Make it roughly 3 cm high
4. Insert a text box near the bottom of (but inside) the frame (Content of the textbox is random). There should be at least about 1cm space between the top border of the frame and the top border of the text box.
5. Resize the frames height by moving the top border down (to eliminate the empty space between border and text box)
Expected: Frame gets resized by moving the top border downwards.
Actual: Bottom border of frame gets moved upwards to accomplish resizing.
IHMO => NAB
Confirmed on Windows 10 Ent 64-bit en-US with recent master
Version: 220.127.116.11.alpha0+ (x86)
Build ID: 489eef894e7034873ad262f9dfca554022db1b09
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win;
TinderBox: Win-x86@42, Branch:master, Time: 2019-10-01_23:43:38
Locale: en-US (en_US); UI-Language: en-US
It is not limited to anchoring 'as character'; same behavior with default anchor for frame 'as paragraph' or the other 'to character', 'to page' anchors behave the same.
Resizing the frame--either with the Frame... dialog's 'Height' spinner, or using its "grips" to drag--will reduce its size from the bottom up, likewise enlarging with grips will add space to the bottom.
So seems size is always relative to top left corner.
But, a potential enhancement? Should the frame resize have an variable anchor point like rotate has a pivot? But strictly internal, ODF should not be an issue--the resize would be complete before writing out the document.
The issue I see is that shrinking the size from top behaves differently than from the bottom. Increasing the size from top adds to the bottom, which is correct as the frame must not expand into the lines above. But making it smaller adds white space at the bottom. This white space is not stored and removed when properties change (eg. enter a value for height in the dialog) or the document is reloaded.
1. Insert > Frame...: Height = 3cm
2. Format > Anchor > As Character
3. Resize per mouse from top
(Spacing:Bottom remains at the same value)
Not an UX issue but a bug IMHO.