Created attachment 160374 [details] Writer doc. showing problem with text flow around an image/frame Version: 6.4.2.2 (x64) Build ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-GB Calc: threaded 1. Open the attached file. Observe pp. 2 and 6. 2. Note that "Frame/Image > Wrap > Top/Bottom" has been made large enough to reserve the whole page for the Frame/Image. EXPECTED RESULT: Paragraph text should flow AROUND the Image/Frame page. ACTUAL RESULT: Paragraph text is not flowing around the Frame/Image correctly. Instead the whole paragraph block is being moved to the page AFTER the Frame/Image. NOTE: Ticking the Orphans box restores the correct flow. The critical conditions for this behaviour are: 1. In "Paragraph style > Text Flow," Orphans is unticked, Widows is ticked. 2. In "Frame/Image > Wrap", Top/Bottom should be set so that Paragraph text cannot fit onto the same page as the Image/Frame and therefore, has to flow around it.
Just for clarification: Page 2 and 6 looks as expected, but problem is blank space on page 1 and 5, correct?
(In reply to Dieter from comment #1) > Just for clarification: Page 2 and 6 looks as expected, but problem is blank > space on page 1 and 5, correct? That's correct. And if you open the "Default (Paragraph) Style" dialog and, on the "Text Foow" tab, tick "Orphan Control", the problem will self-correct.
P.S. I forgot to mention in the opening post that this problem only seems to affect images/frames where the ANCHOR is set "To page."
Created attachment 160556 [details] Simplified document I confirm it with Version: 7.0.0.0.alpha1+ (x64) Build ID: 99c337d1d3831ce9d2c7dc1cbff713f4ac49d6ac CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI: en-GB Calc: CL Steps to reproduce: 1. Open attached document. 2. See text on page 1 covers the whole page 3. Mark image on page 2 => Properties => Wrap => Change spacing bottom to 6,3 cm Result: Blank space on page 1 Expected result: No change on page 1
Also in 3.5
Still present in Version: 7.3.5.2 (x64) / LibreOffice Community Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
Created attachment 189866 [details] Sample with two frames and tabs with fill. Two page sample (file made from scratch). It seems that there are an interaction between the first frame (not anchored to page) and the tabs fill following the second frame (anchored to page). Ctrl + F10 (Toggle Formatting Marks) solves the issue until the next reload. Not an Skia issue. Version: 7.6.0.2 (x86) / LibreOffice Community Build ID: 41d6f628ba3f046f16b5fa9fa8db8d4c2ab3b582 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: es-MX (es_MX); UI: en-US Calc: threaded
(In reply to Dieter from comment #4) > Created attachment 160556 [details] > > Result: Blank space on page 1 > Expected result: No change on page 1 Change the image size to fill the page (11 x 15 cm), set the image space wrapping to 0, and the gap in page 1 appear. There is no gap in page 1, if you unmark the paragraph Widow control.
Dear R. Green, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in Version: 25.8.1.1 (X86_64) Build ID: 54047653041915e595ad4e45cccea684809c77b5 CPU threads: 12; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded