Closed
Bug 161677
Opened 22 years ago
Closed 22 years ago
Preferences > Appearance > Colors horked, JS error
Categories
(SeaMonkey :: Preferences, defect)
SeaMonkey
Preferences
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: glazou, Assigned: caillon)
References
Details
Attachments
(1 file, 1 obsolete file)
1.95 KB,
patch
|
timeless
:
review+
alecf
:
superreview+
|
Details | Diff | Splinter Review |
1. launch Mozilla (trunk) 2. open Preferences 3. choose Appearance > Colors 4. change radio-choice "Always use the colors..." & "Use my chosen colors..." 5. click on OK Expected result : applies changes and closes window Actual result : does not apply change, does not close window, outputs error on console : JavaScript error: chrome://communicator/content/pref/pref-navigator.js line 141: document.getElementById("startupPage") has no properties Tested on Win2K and Linux RH72 with trunk (fresh pull 2002-aug-08 06:00am pacific time)
this makes preferences unusable in the average case
ben: this patch makes the pref dialog handle failures in ok/cancel handlers. we've run into this problem before and it's really really bad for the ok and cancel buttons not to work. -- you've been notified as per the heading of the file, however i do intend to check this in unless you respond quickly indicating why this is much worse than risking users locked in a pref dialog in the event that a cancel and an ok handler throw exceptions
Comment 4•22 years ago
|
||
Comment on attachment 94490 [details] [diff] [review] patch (first half checked in) ok, I'll sr= the first file in that patch, but I refuse to let the 2nd one in - if you're going to touch the file, fix the bug the right way!
Attachment #94490 -
Flags: superreview+
Comment 5•22 years ago
|
||
Comment on attachment 94490 [details] [diff] [review] patch (first half checked in) r=FrodoB (ditto on AlecF's comment). I don't know why the OK and Cancel handlers would fail, but these checks aren't bad to have even if they couldn't. :)
Attachment #94490 -
Flags: review+
Comment on attachment 94490 [details] [diff] [review] patch (first half checked in) ok. I checked the first half in. caillon can now take some time to fix this bug
Attachment #94490 -
Attachment description: patch → patch (first half checked in)
Attachment #94490 -
Attachment is obsolete: true
*** Bug 161733 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 8•22 years ago
|
||
Yes, silly mistake. I thought I had handled that already but I must have reverted patches and went a different route. *sigh*.
Status: NEW → ASSIGNED
Assignee | ||
Comment 9•22 years ago
|
||
Comment 10•22 years ago
|
||
Comment on attachment 94517 [details] [diff] [review] The Real Fix sr=alecf
Attachment #94517 -
Flags: superreview+
Comment 11•22 years ago
|
||
Comment on attachment 94517 [details] [diff] [review] The Real Fix drop 'us' from the comment for r=timeless
Attachment #94517 -
Flags: review+
Assignee | ||
Comment 12•22 years ago
|
||
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 13•22 years ago
|
||
*** Bug 161785 has been marked as a duplicate of this bug. ***
Comment 14•22 years ago
|
||
*** Bug 161835 has been marked as a duplicate of this bug. ***
Comment 15•22 years ago
|
||
*** Bug 161875 has been marked as a duplicate of this bug. ***
Comment 16•22 years ago
|
||
*** Bug 161905 has been marked as a duplicate of this bug. ***
Comment 17•22 years ago
|
||
*** Bug 161933 has been marked as a duplicate of this bug. ***
Comment 18•22 years ago
|
||
btw, this also appears to fix a long standing rfe whereby the current page data is now saved before any of the ok handlers are called, allowing the ok handlers to read the page data without worrying whether the page is current or not, in which case can someone please confirm that in my rfe to remind me to update the patch.
Comment 19•22 years ago
|
||
vrfy'd fixed using 2002.09.16.08 comm trunk builds.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•