Created attachment 169667 [details] WidowControlFootnotes There is an old bug report marked RESOLVED, https://bugs.documentfoundation.org/show_bug.cgi?id=35285, but the discussioon there seems to be somehow intransparent, and I also can't find a solution there. So I'll try again, using a simple example file: The problem ist the failing widow control in footnotes: It often happens that only one line of the footnote is wrapped to the next page, although the widow setting (2 lines) is activated for the footnote and therefore two last lines should be wrapped. It should be the case that the problem basically only occurs with a footnote, inserted in the very last line. (Thanks to mikeleb, https://de.openoffice.info/viewtopic.php?f=1&t=75294, for the demo file.)
Confirm with Version: 7.1.0.3 (x64) / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ro-RO (ro_RO); UI: en-US Calc: threaded
*** Bug 140320 has been marked as a duplicate of this bug. ***
Created attachment 169665 [details] Example file 1. Open the attached file 2. Go to footnote 2 3. Increase Widow Control .. Widow control Specifies the minimum number of lines in a paragraph in the first page after the break. Select this check box, and then enter a number in the Lines box. If the number of lines at the top of the page is less than the amount specified in the Lines box, the position of the break is adjusted. Except 'top of the page' in this case top of footnote; apparently never worked LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
A poke for analysis.. if this 'by design' or some flaw. Touching probably something else, footnotes as such kind of 'error prone' area. So changes will introduce new bugs and/or unmask whole bunch of issues hidden somewhere, being my estimate. JMUX should have some practical experience in this corner of the code
Dear Butch, 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