Description: FORMATTING: I have created a text style, but when I try to edit it it always reverts to the original version. I even tried to create a new style but that too remained the same, as if only one version of a style created by me is possible. The original is Adobe Garamond Pro, Italic, Dark Red. I want it to be Adobe Garamond Pro, Regular, Automatic (Black). I have attempted this edit several times to no effect. Steps to Reproduce: 1. Select my Style proWrite1.5 2. Type text. It comes out as italic in dark red. 3. Workaround - select text, cancel italic and change colour to Automatic. Actual Results: Create a style and then try to edit it. Expected Results: The style remains unchanged from the original. Reproducible: Always User Profile Reset: No Additional Info: It should edit the style. This is a simple process with Microsoft Word and it should be simple for LibreOffice, don't you think? LibreOffice Help does not offer the option Restart In Safe Mode, so I cannot reset my profile. Version: 7.1.8.1 (x64) / LibreOffice Community Build ID: e1f30c802c3269a1d052614453f260e49458c82c CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-GB (en_IE); UI: en-GB Calc: threaded
Hi Rory Thank you for the report. Can you please attach the document for us to test the issue? For resetting your user profile, please go to: "Help > Restart in safe mode > Continue in safe mode", and see if the issue remains. As LibreOffice 7.1 will not be updated anymore, it would be great if you could test a newer version, like 7.2: https://www.libreoffice.org/download/download/
I have tested with the document supplied by Rory via private email and can confirm that clearing the direct formatting of a specific paragraph (or modifying the style) does not restore the font style or the font colour set up in the style. For the paragraph in question, the font colour and the italics are "sticky": they can only be changed by using the formatting toolbar. Waiting for Rory to agree to share the document here for others to test. Version: 7.2.6.2 / LibreOffice Community Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
Dear Rory Fellowes, 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
Created attachment 193729 [details] This is a sample, taking a few paragraphs of my book and adding text set first t o Title and then to proWrite1.5. In both cases, much to my surprise since I never use Title, the bug persists. I hope you can solve this, if not for me (I'm used to it), for others who create their own styles. Thank you.
(I just reset the Assignee field: please only put your email address in there if you plan to submit a patch to fix the issue.) (In reply to Rory Fellowes from comment #4) > Created attachment 193729 [details] Thanks for that document. Looks like the issue is that you have a Character Style with that red colour, called "proWriter1.5_Nitejars. Every time you add a new paragraph, the caracter style persists, and if you remove the direct formatting (which has the black text colour), it will show the underlying character style's red colour. Set your text back to "No character style" and you should be good. You can always use the "Style Inspector" sidebar deck to inspect your text's paragraph/character styles and direct formatting. Closing as "not a bug".