If you go to load styles from a document, the styles all get updates correctly (at least font, font effects, and border settings). However, if you do the same thing from a template file, it only updates the font settings, and not the others. 1. load blank document 2. enter some formatted text (I used headings, changing font type, color, and adding border lines). 3. save document 4. go to "Styles and Formatting" > "Load Styles" and pick either from a templete or From File > and then select a template file. Make sure "Text" and "Overwrite" are selected. 5. document will only change font family/size 6. go back and load styles from an actual document, with "Text" and "Overwrite" and the document will be correctly updated. Expected Results: I would think that all the styles would be correctly updated, regardless of if it's from a template or a document.
I should note that I test from 3.6.7.2 all the way up to 4.4.0.3. The problem from loading from template was in all of them, so it's not new. I'm not sure how far back the loading from document works as I found that correctly working path later. "From File" does seem to work correctly in 4.4.0.3.
Created attachment 113474 [details] Copy of default LibO 4.4 Template
Created attachment 113475 [details] Starting Text File with formatting to see correct results
Created attachment 113476 [details] Altered Formatted Text to use to test loading styles
Reproduced by opening Default Styles-Edited.odt and loading styles from LibO 4.4.ott (with Text + Overwrite enabled). Lowered severity per https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Win 7 Pro 64-bit, LibO Version: 4.4.0.3 Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7 Locale: fi_FI Ubuntu 14.10 Version: 4.4.0.3 Build ID: 40m0(Build:3) Locale: en_US
I should also clarify the bug slightly: 1) loading styles works correctly from a document or a template file if you use the "From File" option. 2) loading styles does not work correctly/fully if you just chose a template from the selector (and you can even be using the same template from point #1).
** 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
** 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.2.7 or 5.3.3 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-20170522
At some point this bug was fixed. It is working correctly in 5.3.3 64-bit on W10 64-bit. I am marking it as resolved -- works for me.