Bug 106153 - Text boxes overlapping the page borders are handled wrong
Summary: Text boxes overlapping the page borders are handled wrong
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: DOCX-Textbox
  Show dependency treegraph
 
Reported: 2017-02-23 11:21 UTC by Jan-Marek Glogowski
Modified: 2019-02-26 22:44 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Overlapping page border text boxes produced with Word 2016 (24.21 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2017-02-23 11:21 UTC, Jan-Marek Glogowski
Details
Example document exported as PDF (87.32 KB, application/pdf)
2017-02-23 11:22 UTC, Jan-Marek Glogowski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan-Marek Glogowski 2017-02-23 11:21:14 UTC
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.
Comment 1 Jan-Marek Glogowski 2017-02-23 11:22:21 UTC
Created attachment 131429 [details]
Example document exported as PDF
Comment 2 Xisco Faulí 2017-02-23 12:12:30 UTC
Confirmed in

Version: 5.4.0.0.alpha0+
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
Comment 3 Luke 2017-02-23 22:20:43 UTC
> 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."
Comment 4 QA Administrators 2018-07-05 02:48:52 UTC Comment hidden (obsolete)
Comment 5 Luke 2018-07-06 21:46:01 UTC
Still not working in Version: 6.2.0.0.alpha0+
Build ID: 61a7a43e3a37e1b1fb764f7be2dc1b5504162ec0