Created attachment 198539 [details] Screenshot showing text-footnote overlay LO 24.8.4.2 Fedora 41, KDE Plasma (VCL=kf6+cairo) I am working on a huge odt document where a footnote inserted in a paragraph very close to bottom of page does not cause note-anchoring line to be flushed to next page so that both the line with the note callout, the separator and the footnote can all be laid out "as expected". Instead the line remains at bottom of page, the separator is inserted (because there is enough space for it), but the footnote is shown ABOVE the separator and thus interferes with text. Text flow properties, split options, of the text paragraph style are: - Keep with next: disabled - Allow to split: enabled, 2 lines at beginning, 2 lines at end Indents & spacing: 0.1 cm above, 0.1 cm below Font size 11pt Footnote style properties: no spacing above and below, same text flow as above, Page style properties: no footer, no borders, 1 column Footnote properties: not larger than page area, space to text 0.6 cm, spacing to footnote 0.4 cm Document has absolutely no direct formatting. The only special point to mention is: the font declared in the style definitions is not installed on my computer. Palatino Linotype is thus replaced by another one. Can this contribute to the behaviour? I am sorry for providing a screenshot instead of an offending document because I could not create a sample case with the behaviour (the original document is ~500 pages).
Possible duplicate with bug 164126
Hello ajlittoz, Thank you for reporting the bug. Can you see if bug 164126 is similar to your problem so that I can mark your report as a duplicate of it? (Later bugs are generally marked as duplicates of earlier bugs). Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Writer: threaded
After checking, it is indeed a duplicate of bug 164126. Mike Kaganski succeeded in creating a sample file reproducing systematically the issue (which I was not able to do from my huge production document). Can be closed as duplicate. I don't know how to include a pointer to 164126 in the preamble of the report. See Also? Or some "stronger" link?