Bug 153691 - Footnotes are unexpectedly split differently across pages after hitting enter
Summary: Footnotes are unexpectedly split differently across pages after hitting enter
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Footnote-Endnote
  Show dependency treegraph
 
Reported: 2023-02-17 13:33 UTC by Telesto
Modified: 2025-03-04 03:10 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Sample (20.27 KB, application/vnd.oasis.opendocument.text)
2023-02-17 16:08 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2023-02-17 13:33:49 UTC
Description:
Footnotes are unexpectedly split differently across pages after hitting enter 

Steps to Reproduce:
1. open the attached file  (a resave of attachment 159138 [details] from bug 131695 with some highlighting applied). See also bug 153689 which closely connected to the issue here
2. Scroll the document. Notice the bottom footnote being highlighting at the first 4 pages
3. Press scroll to top
4. Place cursor in the left table, at the end of the text
5. Hit enter -> freeze occurs (related: bug 131695)
6. Scroll the document.. Notice footnote 78 being followed by footnote 133 and footnote 98 being moved to page 3

Actual Results:
Footnote at the wrong order

Expected Results:
Footnote in the proper order


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 37e3455a13ab5741104bf41d05a80e60a4612682
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 threaded
Comment 1 Telesto 2023-02-17 13:40:25 UTC
Same in
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

and in
Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)

and 
OpenOffice 2.2
Comment 2 Stéphane Guillou (stragu) 2023-02-17 13:56:03 UTC
Can you please attach the file, Telesto?
Comment 3 Telesto 2023-02-17 16:08:21 UTC
Created attachment 185445 [details]
Sample
Comment 4 Stéphane Guillou (stragu) 2023-02-17 21:53:29 UTC
Reproduced in:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b52117c0be97c45824d2897657084f8ac7e9bf42
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
Comment 5 QA Administrators 2025-03-04 03:10:52 UTC
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