Created attachment 87829 [details] writer doc created with styles I noticed 2 problem on my text created with styles. - try to bring chapter 1.1 one level up (also 2.1 and 3.1 if you want). Update index. Index order will change. - try to change screen zoom and the update index. Index order will change. Try to change screen zoom till to have 6 or 8 page on the screen... and see the result.
up
Created attachment 88045 [details] text created with styles
Hi Gioni, I can't reproduce your problem and noticed that Manual:CAPITOLO has no hierarchical style applied (and hence there is no style with level 1) so it may be your first problem. Changing the zoom didn't change the Index too for me - Sophie
Hi Sophie, thank you for your reply. This problem is booring me from at least 3-4 year... By the way, 1- I achieved this result (index order) after several attempts because I have no full knowledge of LO. I will study the problem more deeply. 2- After you change zoom level, you must upgrade index. bye
Miklos Vajna committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=8591de009a4fed6264f236bbcafb2accae70754f Related: fdo#70624 RTF export: fix crash when header contains a page break The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(This is an automated message.) LibreOffice development currently prioritizes bugs with the so called MAB (most annoying bugs) -- as this bug has not run through that process (including writing a short rationale for this bug being a candidate and other who are watching the tracker bug silently approving that rationale etc.) its priority is set to high. Note this is effectively no change in the urgency assigned to this bug, as we are currently not making a difference between high and highest and severity is untouched. You can find out more about MABs and how the process works by contacting libreoffice qa on irc: http://webchat.freenode.net/?channels=libreoffice-qa The QA wiki page also gives you hints on how to get in contact with the team (if IRC fails you, your next best choice is the mailing list): https://wiki.documentfoundation.org/QA
** 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 (4.4.2 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Never confirmed (Miklos's commit references this mistakenly). Is this still a problem in 4.4 or 5.0? Set to NEEDINFO. Change to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
works fine in 4.4.4 great job. thank you
sorry for my previous answer... didn't check the problem issue with the chapter position. This problem still persist in 4.4.4 and in 5.0.0.2 too. The index zoom related problem instead has been solved.
Created attachment 116979 [details] heading in header I thought the columns might have contributed to the out-of-order headings in the Navigator, but I have reduced it to the outline numbering Level 1 style being in the header. In the attachment, the table of contents is correct, but if you remove the empty paragraphs before “Test 1.1” and “Test 2.1”, and update the table of contents, then it will be incorrect. The Navigator shows the headings in the wrong order regardless of there being the empty paragraph or not. Windows Vista 64 Version: 4.4.4.3 Build ID: 2c39ebcf046445232b798108aa8a7e7d89552ea8
NEW per comment 11.
confirmed still a problem with LO5.3beta2 and Ubuntu x64 used bibisect43all oldest to confirm that it has always existed: notBibisectible Steps to reproduce using document from comment 11: -ctrl-click on Test 1.1 in the index and remove the extra CR. Now Test 1.1 is the first paragraph on the page (with Test1 in the header) -go back to the index, right-click and choose update-index. -notice that the order of test1.1 and test1 have switched.
** 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
re-confirmed with 6.3 master.
repro 7.1+
Dear gioni, 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
A heading in a header is a wrong document structure: both because the heading is now outside of the document main text flow, and because it's referenced from a paragraph, so when that paragraph is a heading itself, the order is unclear (some property of the heading paragraph has a reference to a page style, which has a property of a header, which has several paragraphs, one of which is outline property set).