Closed Bug 37897 Opened 24 years ago Closed 24 years ago

Rapidly clicking mouse on preferences renders OK button useless

Categories

(SeaMonkey :: Preferences, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 43223

People

(Reporter: shrir, Assigned: mcafee)

References

Details

I see this on today's linux commercial build (2000050208).

Install and launch the browser
Open Edit->Preferences
Now, starting from top preference,say 'Appearance', click the mouse somewhat 
rapidly (once per second) and go down clicking on all preferences till you reach 
the bottom.
After doing this, clicking on the OK button to close the window does not work.
I see the following message in the console

" Javascript Error: chrome://communicator/content/pref/pref-fonts.js line 173: 
dataObject has no properties "
Perhaps not relevant but see bug 37598 and bug 37708 regarding nightlies:
similar incidents when clicking around in prefs, but other error- and line #'s 
Reassigning as per Don
Assignee: matt → mcafee
Target Milestone: --- → M18
Move to M21 target milestone.
Target Milestone: M18 → M21
Blocks: 40891
This looks like it is a pretty old bug that never got dupped.
http://bugzilla.mozilla.org/show_bug.cgi?id=43223
is the dup of this bug and was first noticed 5/02/00

I'm not really sure if this ever worked actually.
What I can see is happening is that saveFontPrefs()
gets set when you open the fonts pane.  
Then 
parent.hPrefWindow.wsm.dataManager.pageData["chrome://pref/content/pref-fonts.xu
l"] = GetFields();

should get set.
Then you switch to another pane and 
hit ok and saveFontPrefs() gets called but 
parent.hPrefWindow.wsm.dataManager.pageData["chrome://pref/content/pref-fonts.xu
l"] looks the object.
Thus we get this error.

*** This bug has been marked as a duplicate of 43223 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
shrir, d'you disagree? if so, feel free to reopen, heh.
Status: RESOLVED → VERIFIED
no problemo..this is indeed a dup.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.