Problem description: To my opinion not all aspects mentioned in bug 39452 are resolved. The comment list of that bug is quite long. So I tried to disentangle this a bit with new bug reports. This is the first of them. In all Option dialogs exists the button “Revert”. In Versions older than 3.5.x it was called “Back”. In bug report 39452 it has already been discussed, what the correct function of the button “Back” or “Revert” is. There are different possibilities: (1) Getting Started Guide, Chapter 2 – Setting up LibreOffice, section “Choosing options for all of LibreOffice” says: "The Back button has the same effect on all pages of the Options dialog. It resets the options to the values that were in place when you opened LibreOffice." The German tool tip says the same like the Getting Started Guide. (2) The English tool tip says “Resets modified values back to the LibreOffice default values.” I do not believe, that this is the original intention, hence for some options an additional “Default” button exists (e. g. option dialog “LibreOffice Writer > Basic Fonts (Western)”). (3) Only changes of the current options dialog are reverted. This is what happens currently for the most options. May be this is intended, but nearly the same function can be performed by clicking the Cancel button. The difference is that with Cancel the dialog is closed, with Revert it is not closed. (4) Other possibilities ….? So, if there has been a coordinated original intention (what I'm not sure about), I tend to possibility (1). Then possibility (3) would be a bug. In order to reproduce this here the necessary steps: [1] Start LO and open a new text document. [2] Open option dialog: Tools > Options... > LibreOffice > General [3] Change an option, e. g. check “Use LibreOffice Dialogs”. Then OK. The dialog closes. [4] Open the same option dialog again. [5] Click “Revert”. Displayed options don't change. Expected behaviour: Option values should reset to values, that were in place when LO has been opened. That means in this case: Reset of option “Use LibreOffice Dialogs”. I checked this with some other options. The result is always the same, only changes of the current options dialog can be reverted. So it seemed, that the described behaviour is valid for all options. At last a proposal for an improvement of the Revert button: It should be greyed if there is nothing to revert. Operating System: Windows 7
See also bug 58133, bug 58134, bug 58135, bug 58136.
(In reply to comment #0) > So, if there has been a coordinated original intention (what I'm not sure > about), I tend to possibility (1). Then possibility (3) would be a bug. In > order to reproduce this here the necessary steps: > > [1] Start LO and open a new text document. > [2] Open option dialog: Tools > Options... > LibreOffice > General > [3] Change an option, e. g. check “Use LibreOffice Dialogs”. Then OK. The > dialog closes. > [4] Open the same option dialog again. > [5] Click “Revert”. Displayed options don't change. Expected behaviour: > Option values should reset to values, that were in place when LO has been > opened. That means in this case: Reset of option “Use LibreOffice Dialogs”. I can reproduce this behavior using Linux Mint 14 x64 with LO 4.0.0.2 rc2 > At last a proposal for an improvement of the Revert button: It should be > greyed if there is nothing to revert. Agree to that. Following [1] I mark this bug as 'minor medium' because this does not resolve in crash/data loss/etc but resolve in the fact you just can't use some features. [1] https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
*** Bug 61243 has been marked as a duplicate of this bug. ***
** 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.0) 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-02-21
Checked with version 5.1.0, Win7. Meanwhile the name of the button has changed again. It's now called "Reset". But the bug still exists.
** 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.5 or 5.3.0 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-20170306
Bug still exists in version 5.3.0. (Win7) Bug alrady exists in version 3.3.0. Hence inherited from OOo.
** 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
Bug still exists in version 6.0.2 (64 bit, Win 10)
Dear Harald Koester, 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
Checked with version 6.4.2 (Win10). Respective this bug report the help and the documentation have changed: (1) Help of version 6.4.x: "Resets changes made to the current tab to those applicable when this dialog was opened.". And there is a hint that some options can't be reset once edited. (2) Getting Started Guide, Chapter 2 – Setting up LibreOffice, section “Choosing options for all of LibreOffice”, version 6.0 says: "The Reset button, ..., has the same effect on all pages of the dialog. It resets the options to the values that were in place when you opened the dialog. So the behaviour corresponds with the documentation. Hence the bug can be closed.