Created attachment 116843 [details] DOCX for bug demonstration Under certain conditions (probably depending on import from DOCX and on direct formatting), paragraph style is lost after reopening a file. I face this bug quite often when processing files sent by MS Office users. Steps to reproduce: 1. Open the attached file "sample.docx". (It contains two lines of "Normal (web)" style, however heading is formatted directly.) 2. Copy all content of the file (Ctrl+A, Ctrl+C). 3. Create a new file and paste the content to it (Ctrl+N, Ctrl+V). 4. Apply styles (of the default LO template) to the content: "Default Style" to the second line, "Heading" (not "Heading 1" etc.) to the first line. The first line is still directly formatted and does not look like "Heading". 5. Remove all direct formatting (Ctrl+A, Ctrl+M). The first line looks now as expected. 6. Save the file as ODT file. 7. Close the file and reopen it. Observed: The first line has "Default Style" set. Expected: The first line should have "Heading" style. Experienced in all versions I've tested, clean user profile applied: Ubuntu 14.10: 4.3.7.2, 4.4.4.3, 5.0.0.1 Windows 7: 4.4.3.2 to 3.5.4.2 (the earliest I have, bug probably inherited from OOo) Interesting change in 5.0: in step 4, applying the style on the first line removes direct formatting (contrary to earlier versions), so there is no need to remove them manually. However, after doing that, the bug still occurs.
Repro. Win 7 Pro 64-bit, Version: 4.4.4.3 Build ID: 2c39ebcf046445232b798108aa8a7e7d89552ea8 Locale: fi_FI
** 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.1.5 or 5.2.1 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-20160920
Still reproducible in 5.1.5, 5.2.2 and 5.3.0.0alpha0+ from 2016-10-07.
** 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
Still reproducible in: Version: 6.0.0.0.alpha0+, Build ID: 141fe1c5e7fbf67a083b34e49e19b6ea78a0eb2b
Dear Stanislav Horacek, 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
No longer reproduced, was fixed in 6.3.0 since: https://git.libreoffice.org/core/+/43836a58ffe943e2fc65be638f9a7d343102cb07 author Justin Luth <justin.luth@collabora.com> Wed Dec 26 10:49:55 2018 +0300 committer Justin Luth <justin_luth@sil.org> Sat Dec 29 05:11:22 2018 +0100 tdf#47471 odfexport: use stylename if autostyle missing. @Justin: thanks for fixing this one :) *** This bug has been marked as a duplicate of bug 47471 ***
*** This bug has been marked as a duplicate of bug 73483 ***