Created attachment 118834 [details] screenshot Hi, in the attached FODT you'll find a very simple document with a single [Test] Heading 1, however if you open Navigator pane, or export to PDF, you'll see a rogue [Bibliography] heading which is not present in the document at all. In fact it is a <text:h> element in the page styles for the endnote page, a heading in the header, see the following on line 404-408 of the FODT: <style:master-page style:name="Endnote" style:page-layout-name="pm2"> <style:header> <text:h text:style-name="Heading_20_2" text:outline-level="2">Bibliography</text:h> </style:header> </style:master-page> Navigator should not be scanning headings that are only present in page styles and should not show that heading as present. An additional bug is that if you do make an endnote in that document, [Bibliography] is always shown ABOVE [Test], even when it is BELOW it in the actual document. Screenshot shows the document and rogue heading.
Created attachment 118835 [details] Test FODT document test document
Thanks Iandol. I can confirm the behaviour. Already in LibreOffice 3.3.0. May I ask you why a heading could be needed in the header of a page? Cheers - Cor
** 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.1.5 or 5.2.1 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-20160920
Bug persists in 5.3beta1 on macOS. Version: 5.3.0.1 Build ID: 3b800451b1d0c48045de03b5b3c7bbbac87f20d9 CPU Threads: 4; OS Version: Mac OS X 10.12.2; UI Render: GL; Layout Engine: new; Locale: en-GB (en_GB.UTF-8); Calc: group Cor, sorry for the very late reply! This style markup is used by Multimarkdown <http://fletcherpenney.net/multimarkdown/> output to generate a header when applying a style. Perhaps it isn't part of the ODT spec, not sure.
(In reply to Iandol from comment #4) > Cor, sorry for the very late reply! This style markup is used by > Multimarkdown <http://fletcherpenney.net/multimarkdown/> output to generate > a header when applying a style. Perhaps it isn't part of the ODT spec, not > sure. Create a new doc in Writer Insert header and apply Bibliography heading to the paragraph Look in Navigator.. > no header for this. So it looks as a specific case, that is not really a LibreOffice bug?
Cor, my intuition is that LO shouldn't include elements that are outside of the main document in the navigation (they are *impossible* to navigate to!) The <text:h> element is not a child of the main document so why should it be included in the document navigation? Now perhaps ODT doesn't officially allow <text> elements within a <style> block although it currently does work fine (when you apply this style the Heading gets made in the document). Just to be clear: <document> <style><text:h></style> <body> document text </body> </document> The <body> is the content of a file, and the navigator should work on content within the <body> but not link to content in <settings> <scripts> <styles> etc. elements.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170727
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170830