Description: When the "Standard" button is pressed, most attributes are removed (and go back to inheriting from the parent style), but some are not, including numbering style (Outline and Numbering) and some attributes from borders. The numbering style case is particularly problematic, because the UI does not distinguish between "don't do anything" and "no numbering". If you attach a numbering style to a paragraph style and later go back and choose "None", it will mean "no numbering", so subsequent applications of that style forcibly remove all numbering styles as well as manual formatted numbering. I haven't yet checked whether this problem has been reported. The fact that the button is broken was mentioned in bug 42763 comment 4, but I couldn't find a bug report. Bug 89826 is related, but this needs to be fixed regardless. I suspect that this problem has existed since before version 3.3, but for now I'll set the version to 6.0.1.1. Steps to Reproduce: Navigate to relevant tab for some style attribute for some style and press "Standard" then "Apply" or "Okay". Actual Results: All attributes for the tab removed. Expected Results: Some attributes fail to be removed. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
I could not reproduce the Numbering style issue, but from Borders I noticed Width does not reset. Yet, that was the *only* one that misbehaved. The style I modified was picked randomly: Footer paragraph style. Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: 856c57f20f9b07c686a854e0ccbb6ee3b0ee4791 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on March 7th 2018
I think shadows was one of the other properties on the borders tab that refused to reset, in the same manner as numbering. But it sounds like I need to check more thoroughly if you couldn't reproduce the problem with numbering.
(In reply to Kenneth Hanson from comment #2) > I think shadows was one of the other properties on the borders tab that > refused to reset, in the same manner as numbering. Shadow resets fine for me.
** 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
As of v6.3.2.2, problems with borders seem to fixed, at least for a fresh test document. No change to the numbering problem.
(In reply to Buovjaga from comment #1) > I could not reproduce the Numbering style issue It does not work for me. Nor the other controls on that tab get reset to defaulted values for me. Tested with 3.3.0, 5.5.0, and 7.0.2.
(In reply to Mike Kaganski from comment #6) > ... to defaulted values ... I meant "inherited", of course.
Modifying summary to be more informative/accurate. confirm that Numbering Style (now "List Style") does not get reset to the value of the "inherited from" style. and extend the problem to *all* the controls on the Outline & Numbering (or at present "Outline & List") tab. Values for Outline Level and Line Numbering can be changed, but are not reset by "standard". Tested with: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: e60bebd4c5257b0f592d27c74399de1498ac725b CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-US (en_DK); UI: en-US Calc: threaded
Dear Kenneth Hanson, 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
repro On "Outline & List" tab there are three options: Outline Level, List Style, Include this paragraph in line numbering If the values of these options are changed (and applied), then "Reset to Parent" does not reset them to the parent values. Tested with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c41e872ed248f804249ecf4d65c4afc2e426e329 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL threaded(In reply to Mike Kaganski from comment #6) Updating summary (to reflect new labels) Updating version (based on comment 6)
Andreas Heinisch committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/c95f406fcde65e383cff90842ff66e55bfabfc79 tdf#115871 - Reset outline and list options to parent settings It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.