Closed Bug 70593 Opened 24 years ago Closed 24 years ago

"Edit\Preference\Navigator" will not accept changes

Categories

(SeaMonkey :: Preferences, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 66118

People

(Reporter: martin, Assigned: matt)

Details

When altering settings under the Edit\Preferences\Navigator menu item, the "Preferences" dialog windows will not accept an "OK". Only way out is to press "Cancel" thus discarding any change made. Problem does not occur, when altering other settings in the Edit\Preference dialog window...
Please read the component descriptions before picking one ("Unless you're a Mozilla developer, your bug probably doesn't belong in this component"). "Preferences: Backend" means in particular *NOT* problems with the dialog which is by definition FRONT-end.
Assignee: dveditz → matt
Component: Preferences: Backend → Preferences
Martin, could you have a look at bug 66118 if your bug is the same?
To Oliver Klee: After having read bug #66118, I must conclude, that it is not the same. It is actually possible to save changes in the preferences menu, in opposition to bug #66118, so long as you don't make any changes to the navigator settings. To dveditz@netscape.com: Oops. please have me excused... I'll remember that, the next time :-)
tested with Mozilla/5.0 (Windows; U; Win98; en-US; 0.9) Gecko/20010228 sorry i had no problem to press ok if i made any changes to the navigator settings. this only won't work if you switch to history and switch back to any other option. for me this is a dup of bug 66118. reporter: which mozilla version did you use ?
Navigating into Prefs->Navigator categories (e.g. Language, History) are the usual causes for not accepting "OK" button. Well, I think tracking bug #40891 covers this case completely.
*** This bug has been marked as a duplicate of 66118 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
okay
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.