Created attachment 111518 [details] buggy file In OTT file TOC list is blue, but after updating it it becomes normally blue. AFter saving black font and refreshing document - it becomes again blue.
Well the color should be blue because these are links - if you print them they will come out black but on screen they should appear as blue because you can click them to go to that header. Links by default are blue (you can change these in appearance). Marking as NOTABUG. For more information on this please ask on: ask.libreoffice.org or on the user mailing list. Thanks!
Created attachment 111532 [details] stable document No, this is a bug. try to print my doc or convert to PDF, the links would be blue. Here i attach another doc, where links are black, as they should be.
Are you changing the font color for the link from the style Index - contents - font effects? Setting to NEEDINFO, change back to UNCONFIRMED when replying. I can confirm that I'm getting blue text when printed as PDF. Win 7 64-bit Version: 4.5.0.0.alpha0+ Build ID: 57626f2132f73e4e42b31e364b25c5867336e718 TinderBox: Win-x86@42, Branch:master, Time: 2014-12-26_09:26:33
Created attachment 111534 [details] scr The text style is already set to black (in styles), but displayed as blue. If I reload (refresh) TOC - it becomes black. But if i save doc, reopen it - the color will be blue again
Yeah I confirm the experience when refreshing and saving. Setting to NEW.
Just have found Workaround: remove table of contents and add it again. I am happy that I am not to retype all doc Bug still persits, but importance of it should be lowest. There is definetely an error in saving TOC
Lowering priority to lowest.
** 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
linux mint , lo 5.1.5, bug still exists
** 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.4.1 or 5.3.6 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-20170929
Problem still here, 6.0 master
** 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
Wrong ToC line is: <text:a xlink:type="simple" xlink:href="#__RefHeading__1170_269060867">Заголовок 1<text:tab/>1</text:a> Correct line is: <text:a xlink:type="simple" xlink:href="#__RefHeading__1170_269060867" text:style-name="Index_20_Link" text:visited-style-name="Index_20_Link">Заголовок 1<text:tab/>1</text:a> I suggest this bug be closed. It's trivial and it's likely a bug originated in some older LO. I guess it's not likely to be fixed.
(In reply to Timur from comment #13) > Wrong ToC line is: > <text:a xlink:type="simple" > xlink:href="#__RefHeading__1170_269060867">Заголовок 1<text:tab/>1</text:a> > > Correct line is: > <text:a xlink:type="simple" xlink:href="#__RefHeading__1170_269060867" > text:style-name="Index_20_Link" > text:visited-style-name="Index_20_Link">Заголовок 1<text:tab/>1</text:a> > > I suggest this bug be closed. It's trivial and it's likely a bug originated > in some older LO. I guess it's not likely to be fixed. Good point. If we don't have the *steps* to produce this, we can't do much. The blue color is already in 3.3.0.