Reproduce: 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) 6. 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: 6.4.0.0.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 Calc: CL 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.
Dear BottleOnTheGround, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug