Created attachment 119162 [details] ODT file to reproduce the problem In the attached document, you can see that the "Introduction" entry in the table of contents is incorrect: the page number isn't aligned on the right side of the page. This bug happens because I removed the automatic numbering for this heading. If you go to page 3 and remove "Part I" before "Something", and then update the table of contents, you'll get the same for the "Something" entry. This is annoying typically for introductions and conclusions, which use the same heading level as chapters, but without the numbering.
I should have noted that if one adds a line break (Ctrl+Return) in the heading, then the bug disappears.
When I opened it, the pg number for Introduction was aligned correctly. I did repro the "Something" problem, however. Win 7 Pro 64-bit, Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: fi-FI (fi_FI) Version: 5.1.0.0.alpha1+ Build ID: 25de5cfa43b2b1cb7d7214470acc7719839e13fe TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-10-01_08:49:54 Locale: en-US (fi_FI)
If I manual refresh table of contents then it will lost the alignment on the right side of the page (only at level 2). Win 7 Pro 64-bit LibreOffice Version: 4.4.5.2 Build-ID: a22f674fd25a3b6f45bdebf25400ed2adff0ff99 Gebietsschema: de_AT
** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Confirmed with 5.3.0.3 (Fedora 25).
This version: 5.2.5.1 looks ok. Build-ID: 0312e1a284a7d50ca85a365c316c7abbf20a4d22 CPU-Threads: 8; BS-Version: Windows 6.1; UI-Render: Standard; Gebietsschema: de-AT (de_AT); Calc: CL Win 7 Pro 64-bit
But Milan confirmed with 5.3, so let's keep as NEW
(In reply to domf from comment #6) > This version: 5.2.5.1 looks ok. Are you sure you looked at the right line? Only the "Introduction" line shows the bug, the other one is fine, and it's easy to miss the bug (page number where you wouldn't expect it to be).
** 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 present in 6.0.4.2.
Dear Milan Bouchet-Valat, 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 present in 6.1.5.2 (Fedora 29).
Dear Milan Bouchet-Valat, 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://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
Seems to be OK with 7.3.4.2 But I observe in the attachment OP tried to replace the standard outline styling provided by Heading n with some customised set of styles. However, these styles where not assigned outline levels and this was compensated by using the "Additional Styles" in the Type tab of TOC insertion dialog. Also, Tools>Chapter Numbering has been tweaked in a probable attempt to "fix" the misbehaviour. Doing so REQUIRES a deep understanding of document outline machinery. Customising Heading n family would have been sufficient in this case without all the complication introduced by the clumsy replacement. Some of the pacthes are inconsistent: e.g. Chapter Numbering when no paragraph style is attached to outline levels or when a list style replaces the default numbering. It is also obvious OP does not master the non-intuitive subtleties of list style positioning (for his defence, wording is ambiguous because documentation doesn't emphasise the reference position for the numbering and its impact on paragraph formatting). IMHO this bug may result from the complicated implementation of a user outline in a non-optimal way. The bug could be considered if it happened with standard Heading n (which I never experienced, but who knows?). Unless OP confirms he still faces the "bug" (it is seven year old now) and can provide a reproducible sample, I'd close the report. I accept to discuss with OP on private mail if useful.
I still see the incorrect alignment of the page number on the "Introduction" line on 7.3.1.3. After all this time I don't remember what I did and why (this is a simplified example from a more complex document). And it's indeed probably low priority. But I fail to see how the fact that the page number isn't aligned on the right could be considered as not being a bug. (How can you even judge BTW since you say you don't see it?)