The fix of bug 90697 (dupl bug 100513) makes another problem visible: footnotes after the first footnote are pushed to the bottom of the second page. The reference still is on the correct position in the text. This obviously is related to the following problems: - Bug 98287 - Mixing footnotes between sections leads to unwanted page break after the first footnote and pushes the second footnote to the next page (edit) - Bug 54465 - FORMATTING: Inserting footnote in section (with columns), make that sections size grow to the full page This is the test file ( http://bugs.documentfoundation.org/attachment.cgi?id=125792 ) from issue 100513. I'll add a PDF showing part of that file in a daily from June 28, July 4 and a PDF from Word.
Created attachment 126063 [details] pdf with screen prints showing the issue
Version: 5.3.0.0.alpha0+ Build ID: 28a03248b1d1649e157b788e43dfe8326f165379 CPU Threads: 2; OS Version: Linux 3.16; UI Render: default; Locale: en-US (en_US.UTF-8) Confirmed.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
still the same problem in Version: 6.1.0.0.alpha0+ Build ID: a9b202a6b7000e7af34f2a639ca207122a3968bf CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-12-26_23:09:36 Locale: nl-NL (nl_NL.UTF-8); Calc: group threaded
problem persists in Version: 6.3.0.0.alpha0+ Build ID: 082144fa0fb2021cfb41494bb6eb5bf417e58ab1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2018-12-31_03:11:43 Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 175319 [details] Minimized example file This Word 2019 minimized file contains no section break, but the footnotes are laid out differently in Writer regardless. There is a textbox in the footer and upon opening this file in Writer there is only one footnote laid out on the first page. However selecting the textbox in Writer, pressing Del, then choosing Tools - Update - Page Formatting moves the footnotes 2-3 to the bottom of the first page, just like in Word.
Created attachment 175320 [details] The minimized example file in Word and Writer side by side
Dear Cor Nouws, 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
I cannot reproduce with Version: 25.2.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 905e7c1105536c9757fa2c2faf670738aab02595 CPU threads: 8; OS: macOS 15.0; UI render: Skia/Metal; VCL: osx Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
(In reply to Jiří Nováček from comment #10) > I cannot reproduce with indeed - thanks!