Description: Page layout off/ should be 4 for pages Steps to Reproduce: 1. Open the attached file 2. Image on page 3 is overlapping text with optimal text wrap on Actual Results: Image on page 3 is overlapping text Expected Results: Same as LibreOffice 3.0 Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 7.0.0.0.alpha0+ (x64) Build ID: 951b6a9570ae2665f7b6e7cdd6d24d1fc513ba90 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL but not in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Created attachment 159934 [details] Example file
Created attachment 159935 [details] Demonstration 1. Open the attached file 2. Select the image 3. Drag the anchor to page 4 4. Result -> Example file
No repro 4.3. Then 4.4 and 5.0 missing text. Repro 5.2 and 7.1+. Regression. Needs 2 bibisects.
(In reply to Timur from comment #3) > No repro 4.3. Then 4.4 and 5.0 missing text. Repro 5.2 and 7.1+. Regression. > Needs 2 bibisects. Select the image and move it a little in older versions.. and result will be the same.. already seen in 4.0 oldest
(In reply to Timur from comment #3) > No repro 4.3. Then 4.4 and 5.0 missing text. Repro 5.2 and 7.1+. Regression. > Needs 2 bibisects. Above test was in Windows, just opening file. But try to bibisect in Linux with 4.4 showed it's not that simple, same version opens differently. Looks like it depends on zoom. For example, 50% zoom opens 3 pages (wrong) in 4.4 oldest, same as latest. 75% zoom opens differently in oldest, 3 or 4 pages (wrong or correct). Going back to OO 3.3, it will mostly open fine, but not always, so this looks Inherited. Also in master 7.1+, 75% zoom opens differently.
Looks like the key issue here is multipage view. If file (even wrong with 3 pages) is saved with single page (100% or 75%), it opens fine after that.
*** Bug 133709 has been marked as a duplicate of this bug. ***
(In reply to Timur from comment #7) > *** Bug 133709 has been marked as a duplicate of this bug. *** Sorry, I missed noticing this duplicate marking earlier. Can you explain why - since this inherited bug is referencing a 7.0 regression? I'm trying to decide whether I do go ahead and revert the identified commit in bug 133709 as I originally intended, or whether I just wash my hands of it and let it stay. Would reverting help this bug in any way, or hurt it even more.
(In reply to Justin L from comment #8) > (In reply to Timur from comment #7) > > *** Bug 133709 has been marked as a duplicate of this bug. *** > > Sorry, I missed noticing this duplicate marking earlier. Can you explain why > - since this inherited bug is referencing a 7.0 regression? > > I'm trying to decide whether I do go ahead and revert the identified commit > in bug 133709 as I originally intended, or whether I just wash my hands of > it and let it stay. Would reverting help this bug in any way, or hurt it > even more. I missed it too :-). Seems unrelated to me.
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