Problem description: Upon restart or reactivation the menu options under LibreOffice Writer / Formatting Aids have no effect. Regardless of what characters you chose to show, all get reactivated after switching the formatting aids off and on again. Steps to reproduce: 1. Open any document of your choice 2. Activate the Formatting Aids (Strg + F10) 3. Change the Formatting Aids options under Preferences / LibreOffice Writer / Formatting Aids to show none of the available menu options 4. Hit save and go back to your document. You will now see that the only available Formatting Aid is the pager border. 5. Deactivate the Formatting Aids (STRG + F10) 6. Reactivate them (STRG+F10) 7. Result: initial Formatting Aids configuration is restored. All nonprinting characters are visible again Current behavior: http://www.youtube.com/watch?v=PR9ssogeGc4 (please do not pay attention to the audio, it was recorded out of mistake) Expected behavior: Checked and unchecked states of menu options under Preferences / LibreOfffice Writer should be properly stored and persist until manually changed by the user. Platform (if different from the browser): Ubuntu 12.04 LTS Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.81 Safari/537.1
I am sorry, I had uploaded the wrong video so I had to remove it. New video is on its way.
Alright, here you go: http://www.youtube.com/watch?v=_EhW2eQ56n4 This is the current behaviour with LibreOffice 3.6.0.4 on Ubuntu 12.04 LTS.
Hi Mark, Thanks for posting. I see that when I use View > Text boundaries and can set the borders to work how they should. But I've not yet found out, if it is complicated work-flow or my lack of understanding of it ;-) Maybe you can have a look? Cor
(In reply to comment #3) > Hi Mark, > > Thanks for posting. > I see that when I use View > Text boundaries and can set the borders to work > how they should. > But I've not yet found out, if it is complicated work-flow or my lack of > understanding of it ;-) > Maybe you can have a look? > Cor Hey Cor, thank you for your comment. You are right, the page borders are correctly shown if both the "Formatting Aids" option and "Text boundaries" are active. What doesn't work is customizing what is shown in addition to the borders when activating Formatting Aids. In my case for instance, I wanted to disable paragraph and line break markers to only show the page borders. In previous versions of LibreOffice you were able to define which nonprinting characters should be visible and which should not be. You could choose the characters you wanted to see from the options menu (Options --> LibreOffice Writer --> Formatting Aids). That option does not work correctly in this version. Initially your changes are saved. As soon as you deactivate the "Formatting Aids" option, however, the program forgets the changes you have made and goes back to the initial configuration when Formatting Aids are activated again. Mark P.S.: If the Formatting Aids are disabled, the Text boundaries option just controls the visibility page corners. Only with previously activated Formatting Aids you can control the visibility of page borders.
the resetting of "formatting aids" when clicking the non-printable toolbar button happens in LO 3.5, LO 3.4, OOo 3.4beta, OOo 3.3, OOo 3.2.1 and OOo 3.0.1 => not a regression
Confirmed still present in 3.6.1.2. Easiest way to reproduce: 1. go into options, libreoffice writer, formatting aids and uncheck all from the first column. 2. press ctrl+f10 three times visible marks for the following items return: paragraph end spaces tabs breaks hidden text The above items also have checkboxes in the relevant options screen again. This is under Arch Linux, specific build info: "(Build ID: 3.6.1.2 ArchLinux build-4)" Interesting other behaviour: The formatting aids setting *is* correctly retained across save/close/exit, so long as the user does not toggle "View non-printing characters".
I do not reproduce with LO 3.6.1 nor master (Build ID: 2ecd5b0) under Ubuntu 12.04 with gnome-shell. Best regards. JBF
(In reply to comment #7) > I do not reproduce with LO 3.6.1 nor master (Build ID: 2ecd5b0) under Ubuntu > 12.04 with gnome-shell. Oups, sorry I read the bug description too quickly. It works for me as expected when I check all checkboxes.
(In reply to comment #8) > (In reply to comment #7) > > I do not reproduce with LO 3.6.1 nor master (Build ID: 2ecd5b0) under Ubuntu > > 12.04 with gnome-shell. > > Oups, sorry I read the bug description too quickly. It works for me as > expected when I check all checkboxes. Sorry, I don't understand. What happens if you: 1.) uncheck all checkboxes 2.) go back to the document and activate/deactivate formatting aids (CTRL +F10) In my case all unchecked formatting aids reappear. The selection (all unchecked) didn't get properly saved. Can you reproduce the bug this way?
To keep your settings for non-printing characters, it seems there is two conditions: 1/ first show the non-printing characters by ctrl+F10 then change the settings. 2/ keep checked at least one non-printing character. Best regards. JBF
(In reply to comment #10) > To keep your settings for non-printing characters, it seems there is two > conditions: > 1/ first show the non-printing characters by ctrl+F10 then change the > settings. > 2/ keep checked at least one non-printing character. > > Best regards. JBF Thank you, this works fine. Still, I'd consider this more of a workaround than an actual solution. Maybe the problem lies with the available checkboxes. I think it would make sense to include a checkbox for page borders. That would solve the confusion around the formatting aids options. Greetings, MW
Thank you for reporting this issue! I have been able to confirm the issue on: Version: 4.2.0.0.alpha0+Build ID: b0a1666f756aa5f5315366eca9d7d02ddd55d2b Date: Tue May 28 08:51:01 2013 +0300 Platform: Bodhi Linux 2.2 x64 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + As I've been able to confirm this problem I am marking as: New (confirmed) Minor - can slow down professional work but doesn't prevent it Low - default seems appropriate
is inherrited behaviour from old OOo, conform comment 5
** 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 (4.4.1 or later) 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: 2015-03-16
(In reply to Felix from comment #6) > Confirmed still present in 3.6.1.2. Easiest way to reproduce: > > 1. go into options, libreoffice writer, formatting aids and uncheck all from > the first column. > 2. press ctrl+f10 three times > > visible marks for the following items return: > > paragraph end > spaces > tabs > breaks > hidden text > > The above items also have checkboxes in the relevant options screen again. Reproduced. Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+ Build ID: 8c3cf9dd48e40604867d3a28bddaccd65142df17 TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-03-27_15:15:18 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 LO 5.2.3.0+ and current master, both built at home under Ubuntu 16.04 x86-64. Best regards. JBF
** 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 LO 6.1.1.0.0+ and current master, both built at home under Ubuntu 16.04 x86-64. Best regards. JB
Dear Glutanimate, 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 LO 6.3.1.0+ and current master, both built at home under Ubuntu 18.04 x86-64. Partial workaround from comment #10 still works too. Best regards. JBF
Repro 7.2+.
Dear Glutanimate, 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