Description: Wrong information about table of contents' formatting is shown. Steps to Reproduce: 1. Create a document with 3 headings 2. Insert a Table of Contents 3. Click onto ToC and set font to Arial Actual Results: ToC has right formatting but in the top left corner the information for font, size (maybe bold, etc. too?) is wrong. Short note: It could be also that if I regenerate ToC that for new entries in an existing ToC, the paragraph's template is ignored and default formatting of ToC is applied. Someone should try to verify this. Expected Results: I can select specific parts of the ToC or simply all and I can see which formatting is applied so I know what is going on. Reproducible: Always User Profile Reset: No Additional Info: Version: 5.3.7.2 (x64) Build-ID: 6b8ed514a9f8b44d37a1b96673cbbdd077e24059 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
How to you do step 3? The ToC is write protected in the default work flow of step 2.
I do right click on ToC -> change paragraph's template/style -> change Liberation Sans to Arial in the new window.
You can edit the paragraph style in the Styles&Formatting window as well in step 3. The items are not updated, because the ToC is write-protected. But I agree with you, although the user cannot use the items, they should always show the current value. There is a similar problem for protected sections, because a ToC is actually a section. The paragraph style field shows the correct style name, if you click on a line in the ToC. [You can select a new style there, but it has no effect in protected sections. But that might be a different error.]
I have to disagree with you if I do understand you correctly. If I choose a different font in the paragraph's style window, this change is reflected in ToC. I added a screenshot to show you.
Created attachment 138005 [details] example of ToC with changed font
The issue is not about the ToC itself but about the font field in the Formatting toolbar. And it is not specific to ToC, but can be seen for all protected sections.
** 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
Repro 6.3+. Looks like a duplicate of Bug 73031. *** This bug has been marked as a duplicate of bug 73031 ***