Description: Dragging dropping of footnotes cause breaking text differently (and inefficient) Steps to Reproduce: 1. Open the attached file 2. Select footnote 1 and 2 3. Drag it to the orange area Actual Results: Text moves to second page Expected Results: No change, did fit before.. so why split? Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: d851a02df57ab378ed0cc6d9362516de09c3279c CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Created attachment 163255 [details] Example file
Delete footnote 1/2 and you see the same 'quirky behavior'
4. Select the image.. press arrow up 5 times.. text should be as expected. Press arrow down once and it jobs again
Created attachment 163256 [details] Screencast
I see the complained-about behaviour in a local build of commit 7b44eb2c (2020-07-22) built and running on debian-buster. My search for duplicate reports turns up: (*) bug 134444 Moving image down overlapping footnotes, and backup moves image down This looks like what Telesto mentions in comment 3. (*) bug 134189 A page layout loop hitting icu_67::RuleBasedBreakIterator::handleNext over and over Definitely a see-also. (*) bug 129747 Several footnotes in a multipage table causes massive display and formatting problems At least a see-also. Could be DUP based on "suddenly jumped to the second page" in description. Telesto, what do you think about these other bugs? Meanwhile, I am setting status NEEDINFO; you know what to do.
Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Still present Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: c38d0d501f5eca648bdf0fd2914b57e06f505f7e 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
Also in 4.4.7.2 and in Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)
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