Closed Bug 161875 Opened 22 years ago Closed 22 years ago

OK fails to save changes and exit prefs

Categories

(SeaMonkey :: Preferences, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 161677

People

(Reporter: mrmazda, Assigned: bugs)

Details

(Keywords: regression)

OS/2 trunk 2002080808

A day or three ago I enabled "allow scripts to open unrequested windows" and
forgot to change it back after finishing with a site that wouldn't work without
it. Now I'm stuck with it. Nothing I do in prefs UI will make that checkbox stay
unchecked. I switch to other prefs sheets, and still OK refuses to exit prefs
with save. Only OK will exit prefs. Eliminating user.js also fails to help.
Going back to 2002080708 solves the problem.
s/Only OK will exit/Only Cancel will exit/
My 'open unrequested windows' is currently turned off. After enabling, the OK
doesn't work. This with Linux 2002080808

Error in javascript console:
Error: document.getElementById("startupPage") has no properties
Source File: chrome://communicator/content/pref/pref-navigator.js
Line: 141

keyword: regression, OS: all
Keywords: regression
OS: OS/2 → All
I'm setting Severity to 'critical', since this needs an immediate fix. BTW, I
don't think this has anything to do with 'open unrequested windows'.
Severity: major → critical
I think my comment was unclear. I went to Preferences-> Advanced-> Scripts and
Plugins; changed the pref 'open unrequested windows' from not checked to
checked; then tried to press OK. After this the OK didn't work (Cancel does).

Tried it again. After switching from the Navigator part to somewhere else, the
OK stops working. You can change prefs and press OK on the Navigator page, but
not after changing to another prefs page.
hrm.. this is a dupe... fix was checked in.

*** This bug has been marked as a duplicate of 161677 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
What I get for query on "prefs" instead of "pref".
vrfy dupe

i don't think this bug was critical since it was fixed 14 hours before it was filed.
Severity: critical → normal
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.