Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 207739

Summary: CVS prefs: Restore Defaults then Cancel saves anyway
Product: [Eclipse Project] Platform Reporter: Arnaud Lucien <IngedevTeam.fr>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 Keywords: helpwanted
Version: 3.3.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Arnaud Lucien CLA 2007-10-29 05:32:10 EDT 
Build ID: M20070921-1145

Steps To Reproduce:
1. Open the CVS pref page and set a preference to a value other than the default one (e.g. max number of comments = 1). Click OK.
2. Open the same page again. Click Restore Defaults, this indeed restores the fields to their default values.
3. Click Cancel - this should cancel the previous "Restore Defaults".
4. Reopen the same page: the fields have been reset to their default values.


More information:
Comment 1 Tomasz Zarna CLA 2007-11-06 09:46:40 EST 
Affirmative, the "Restore Defaults" button seems to save the values not waiting for neither "Ok" nor "Cancel" to be clicked. The good news is that the Team preference pages look to be working fine. 

Patches are welcome.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:04:00 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 3 Eclipse Genie CLA 2021-09-12 13:13:58 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.