Created attachment 114326 [details] formatting.odt: select all, make red font color, clear direct attributes, make red again and save. 1) Open a new document, insert some "Heading 1" and some "Body Text" under it. 2) Select it all and color it red. 3) Clear direct formatting. 4) Color it red again and save the document. 5) After reopening the document, the "Heading 1" lacks the red color.
Reproducible with LO 4.4.1.2, Win 8.1
Occurs all the way back to OOo / LO 3.3.0 -> Version: Inherited from OOo
** 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.0.5 or 5.1.2 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: 2016-04-16
Still there in LO 5.1.2 on Windows 10 x64.
** 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
Seen in: Version: 6.1.1.1 Build ID: 1:6.1.1~rc1-2 CPU threads: 4; OS: Linux 4.2; UI render: default; VCL: x11; Locale: en-US (en_US.utf8); Calc: group threaded
Still in 6.2.0.1.
After 2): <text:h text:style-name="P3" text:outline-level="1">h1</text:h> <text:p text:style-name="P2">tb1</text:p> <style:style style:name="P3" style:family="paragraph" style:parent-style-name="Heading_20_1"> <style:text-properties fo:color="#c9211e"/> <style:style style:name="P2" style:family="paragraph" style:parent-style-name="Text_20_body"> <style:text-properties fo:color="#c9211e" officeooo:rsid="0002cb8e" officeooo:paragraph-rsid="0002cb8e"/> After 3): <text:h text:style-name="Heading_20_1" text:outline-level="1">h1</text:h> <text:p text:style-name="Text_20_body">tb1</text:p> After 4): <text:h text:outline-level="1">h1</text:h> <text:p text:style-name="P1">tb1</text:p> <style:style style:name="P1" style:family="paragraph" style:parent-style-name="Text_20_body"> <style:text-properties fo:color="#c9211e"/>
Justin, since you're already on Bug 47471, can you please check whether this is a duplicate?
No, it is not a duplicate, but highly related. 0.) round-trip file. Paragraph 1 saved with style Heading 1 1.) apply red color and save: Paragraph 1 saved with autostyle P2. 2.) clear direct formatting and save. Paragraph 1 saved with style Heading 1. 3.) re-apply red color and save: Paragraph 1 has an empty autostyle. In fact, I'm kinda surprised that the Heading 1 style isn't lost altogether and that it didn't revert to default style. It seems like this is a missing notification / missing cache flush scenario? Probably a fix for this would also fix bug 47471.
I should also have mentioned, if you hit <enter> after Heading 1 in the text, that is enough to "re-generate" the new P# autostyle.
Repro 6.4+
repro 7.1+
@Michael, may I CC you on hard bugs that no one else will be able to solve?
I just tested all paragraph style. Only "Heading 1" - "Heading 10" are affected. Plain "Heading" is not affected. I will attach the document I used to test.
Created attachment 163372 [details] One paragraph per style. Currently bugged. This is the document I used so you can use it to test too. For each style, it has one paragraph which contains the name of the style, formatted with that style.
Dear tomaskeb, 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 7.6+
*** This bug has been marked as a duplicate of bug 73483 ***
(In reply to Mike Kaganski from comment #19) > > *** This bug has been marked as a duplicate of bug 73483 *** I don't know whether this is a duplicate or not, but 73483 is supposed to be solved from 7.5.5 on and Justin L reproduced this 90221 on a 7.6+ version. It seems to be an evidence against this bug to be properly marked as RESOLVED.
(In reply to Fede from comment #20) > Justin L reproduced this 90221 on a 7.6+ version. I tested on May 15, and Mike's patch landed on May 30. Status is OK.
(In reply to Justin L from comment #21) > (In reply to Fede from comment #20) > > Justin L reproduced this 90221 on a 7.6+ version. > I tested on May 15, and Mike's patch landed on May 30. Status is OK. Sorry, I paid attention to version numbers, but not to dates. My bad. However, it's not the first time that bugs related to side effects of cleaning direct formatting are announced as fixed, but that cleaning keeps on producing undesired side effects. Along years and years. So please try to understand my mood regarding this. I hope this time will be different. Thanks for working on this.