Created attachment 65563 [details] Sample document illustrating the drop of bold attributes on heading text. Problem description: Manually bolding then unbolding (using ctrl b) in paragraph text will cause subsequent headings to lose the bold attribute. Steps to reproduce: 1. Open a new document 2. Select Heading 1 from the styles 3. Type a heading (it will be bold) 4. Press enter for a new paragraph (style will be Text Body) 5. Type some lines. Press ctrl-b to start bold, type some more, then ctrl-b to stop bold and type some more. 6. Press enter for a new paragraph 7. Select Heading 2 from the styles 8. Type (heading will not be bold). Current behavior: Headings are not bold even when their style says they should be. Expected behavior: Headings should adhere to their styles. Platform (if different from the browser): Browser: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6) Gecko/20120714 Firefox/10.0.6
As far as I recall, it affects all platforms I use (Linux 32 and 64bit, and windows).
Confirmed with 3.6.4 and 4.0.0.beta1 on XP SP3, with new documents.
Still repro Version: 4.4.0.0.alpha0+ Build ID: 2e01d1bc5cd5186973d0451e8e9beaf3a924bcea Kind regards, Joren
Probably same issue as in bug 69495. Also, appears to be fixed in LO 5 beta 1. (Tested against RHEL6 x64). Can someone verify and close?
** 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
Created attachment 140684 [details] A file demonstrating this bug This bug seems to be hard to reproduce. I don't get it most of the time, but this file demonstrates it. Just type a new line (sorry, it's Hebrew, but you can write in English and it would show regardless) and apply Heading 1 style. It won't be bold. This seems to be some formating bug because when copying the text with formatting into a new document, the new document still demonstrates this bug.
The bug is not reproduced in version below Version: 6.3.0.0.alpha0+ (x64) Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55 Locale: zh-TW (zh_TW); UI-Language: en-US Calc: threaded
Dear TJT, 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
(In reply to eladhen2 from comment #6) > this file demonstrates it. Just type a new line (sorry, it's Hebrew, > but you can write in English and it would show regardless) and apply > Heading 1 style. It won't be bold. Using attachment 140684 [details] 1. Hit return, click on Heading 1 (in empty paragraph), then type. Text appears with Heading 1 attributes (i.e., bold, etc.). 2. Follow procedure described, add a line, then apply Heading 1. It is not bold as reported. But, now select the added line and Format -> Clear Direct Formatting (now the line appears in bold with Heading 1 attributes). In other words, the test case does not really show any bugs. The "missing bold" was because of direct formatting applied to the text in the "next line". Also, cannot reproduce the original STR. Tested with: Version: 7.0.0.0.alpha0+ (x64) Build ID: cf96cb11e2a46c452a273ded1c66c556118983cf CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; Locale: en-US (en_DK); UI-Language: en-US Calc: threaded In combination with comment 7, closing as WFM.