Description: A new page is added when moving an image to certain spot (since 6.5) Steps to Reproduce: 1. Open the attached file 2. Select the image 3. Press arrow down once -> Empty page 4. Press arrow down 2x -> text moves up again Actual Results: Empty page is added however not expected Expected Results: No empty page Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: c48e4d795e37f23b71d647247590807ab9e52223 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
Created attachment 162733 [details] Example file
Not in 6.4
@Buovjaga Are you still saving bibisects? This one is rather easy to do
(In reply to Telesto from comment #3) > @Buovjaga > Are you still saving bibisects? This one is rather easy to do Yes, I have a teaching session tomorrow. I will reserve this until then. I won't reserve these fresher ones forever - I will bibisect the remaining ones this week myself, if needed. This should be bibisected with 7.0 repo.
This wasn't a very good pick for teaching after all - at the start of the session I suddenly saw this even in the oldest commit of 7.0 repo and latest of 6.4. Today I can't see it in the latest of 6.4 repo. I can not seem to be able to find a reliable way to reproduce.
(In reply to Buovjaga from comment #5) > This wasn't a very good pick for teaching after all - at the start of the > session I suddenly saw this even in the oldest commit of 7.0 repo and latest > of 6.4. Today I can't see it in the latest of 6.4 repo. I can not seem to be > able to find a reliable way to reproduce. I couldn't reproduce with linux repo, but with windows got this: This was the first bad commit: a0ea81b7a7bca12c7e347da7987c8c3574d61503 . Bibisected using bibisect-win64-7-0. to: URL: https://cgit.freedesktop.org/libreoffice/core/commit/?id=74c882c39ebeb5b9de531271a6d757cbe8780691 author: andreas kainz <kainz.a@gmail.com> committer: andreas kainz <kainz.a@gmail.com> summary: Same grid layout in all apps for better arrangement and presets Adding CC: andreas kainz
(In reply to Attila Baraksó (NISZ) from comment #6) > (In reply to Buovjaga from comment #5) > > This wasn't a very good pick for teaching after all - at the start of the > > session I suddenly saw this even in the oldest commit of 7.0 repo and latest > > of 6.4. Today I can't see it in the latest of 6.4 repo. I can not seem to be > > able to find a reliable way to reproduce. > > I couldn't reproduce with linux repo, but with windows got this: > > This was the first bad commit: a0ea81b7a7bca12c7e347da7987c8c3574d61503 . > > Bibisected using bibisect-win64-7-0. to: > URL: > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=74c882c39ebeb5b9de531271a6d757cbe8780691 > author: andreas kainz <kainz.a@gmail.com> > committer: andreas kainz <kainz.a@gmail.com> > summary: Same grid layout in all apps for better arrangement and presets > > Adding CC: andreas kainz The result is not correct. The blank page also appears in the preceding commit.
Older. Open with 3 pages with LibO 3.3 Another way to reproduce 1. Press Arrow down until image reaches bottom 2. Up again -> Empty page will appear Another of my beloved anchoring bugs
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