Description: Image before text on file open Steps to Reproduce: 1. open the attached file Actual Results: Image before text on file open (no wrap) Expected Results: Wrap Reproducible: Always User Profile Reset: No Additional Info: Repro with Version: 7.1.0.0.alpha0+ (x64) Build ID: <buildversion> CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL and in with 6.0 and with 4.4.7.2 not with 4.3.7.2
No attached document
Created attachment 163704 [details] Example file
Confirmed with 7.1.0.0.alpha0+ (abea0d6647c7f1f7e76c73c26cb80e6a67dc5111) / Ubuntu. Bibisected to the following commit using repo bibisect-44max. It's the same result as for bug 133975. https://cgit.freedesktop.org/libreoffice/core/commit/?id=133d6d8d4dec497276c3a9b0ba6761cffd322f81 author Oliver-Rainer Wittmann <orw@apache.org> 2014-07-15 12:15:37 +0000 committer Caolán McNamara <caolanm@redhat.com> 2014-07-16 09:01:02 +0100 Resolves: #i121443# register text frames and graphics...
Created attachment 163792 [details] Example file 2 (only slow loading. no wrap issue)
@Caolán Any idea why this and bug 133975 is happening. You're not the author, but did commit this. As for bug 133975, I assume this commit only accelerating something. They empty page issue is certainly not new (Enough goes back to OoO days based on my reported bugs); but the commit isn't helping either
no idea, those are just merges of the AOO work when it was still an active project
Created attachment 171207 [details] How the document looks before the commit
Still reproducible in Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: a199e4ea389c934d169a178433f4b94033e60f93 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
The issue is not reproducible if the document is converted to PDF using the commandline...
This is an extremely fake example, where one paragraph takes up multiple pages, and images aren't anchored intelligently at all. So we get layout glitches. It seems pointless to have this bug report existing. There is a LOT of layout churn just trying to get the algorithm to stabilize.
*** Bug 147155 has been marked as a duplicate of this bug. ***
https://gerrit.libreoffice.org/c/core/+/150637 is debug statements for related META bug 154703 comment 11's attachment 186670 [details] layout issues. Too many pathways for my brain to handle, and to much wrong on a grand scale - not just a minor wrong calculation but fundamental issues here. Fundamental issues on a fragile base is not somewhere I should be.
Dear Telesto, 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 Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7fac8458e35620b9855cc6c68a9675159a849b65 CPU threads: 8; OS: macOS 14.7.4; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded