Created attachment 131428 [details]
Overlapping page border text boxes produced with Word 2016
This bug is about a more general handling of text boxes overlapping the page borders. A partial fix - for a text box overlapping the bottom - was developed to fix bug 91260. It doesn't seem to work with the attached document generated by Word 2016.
The attached document has four text boxes, all overlapping one of the page borders. The placement of the text part of the boxes is wrong, as they seem to be forced completely inside the page frame. But the associated shapes seem to be correctly placed.
This also results in UX bugs:
* if you try to select the frame of a text box, it "correctly" selects the shape.
* if you try to move the frame, the whole text box is forced inside the page borders
In MS Word 2016 I actually had to change the layout options to move the text box out of the frame borders, when generating the test document.
So my guess is the logic of commit a4dee94afed9ade6ac50237c8d99a6e49d3bebc1 is wrong, as it breaks the synchronization of the text and shape frame. Probably this really has to be handled separately.
Created attachment 131429 [details]
Example document exported as PDF
Build ID: 880033edde516fc30225005245253293a6a58ba4
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
> So my guess is the logic of commit a4dee94afed9ade6ac50237c8d99a6e49d3bebc1
> is wrong, as it breaks the synchronization of the text and shape frame.
> Probably this really has to be handled separately.
The issue of imported TextBoxes not moving with the shape is likely an implementation bug. See Comment 14 on Bug 84678#c14
"And when you move [our TextBoxes] the text doesn't stay in the Text Box, which kind of defeats the whole point of Text Boxes."
** Please read this message in its entirety before responding **
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 http://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!
Still not working in Version: 126.96.36.199.alpha0+
Build ID: 61a7a43e3a37e1b1fb764f7be2dc1b5504162ec0