Closed Bug 79821 Opened 24 years ago Closed 23 years ago

cannot switch classic theme: changing and clicking OK gives an error on the Javascript console

Categories

(Core :: XUL, defect, P3)

Product:
Core
Component:
XUL
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Milestone:
mozilla1.0.1

People

(Reporter: mwyner, Assigned: bugzilla)

References

Details

I downloaded the May 9th nightly build on Solaris. Went to "preferences" to change my theme from classic to modern, selected the modern theme, and clicked "apply". Then clicked "ok" to get rid of the preferences window. The window didn't go away, instead I got the following JavaScript error: JavaScript error: chrome://communicator/content/pref/nsPrefWindow.js line 209: this.wsm.contentArea.document has no properties Clicking on the "cancel" button doesn't result in this and the preferences window will go away (as a workaround).
*** Bug 79413 has been marked as a duplicate of this bug. ***
It wasn't *when* I changed my theme to modern, but it was after that, that I encountered this bug. I still haven't been able to recreate it, but I also haven;t changed my theme back.
it happened on my Forte5 xlib build. updated a few hours ago.
Blocks: 79119
*** Bug 82011 has been marked as a duplicate of this bug. ***
->all, since it happens on linux and win32 [see dups].
Blocks: 40891
Keywords: nsbeta1
OS: Solaris → All
Hardware: Sun → All
nav triage team: Reassigning to Ben. Ben, can you look into this and tell us if it's a beta stopper
Assignee: mcafee → ben
Priority: -- → P2
Target Milestone: --- → mozilla0.9.2
This doesn't seem like my bug. It's as if the window is getting trashed on the theme switch or something. This has happened before, however since the apps code has worked in the past, it seems that this is a toolkit issue not a fe issue.
nav triage: based on frewuency of occurrence, downgrading to p3, moving to m0.9.3.
Priority: P2 → P3
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Keywords: nsbeta1 → nsbeta1+
*** Bug 82942 has been marked as a duplicate of this bug. ***
*** Bug 80218 has been marked as a duplicate of this bug. ***
Updating title to ease the search... This bug has been reported several times probably because it was hard to find.
Summary: changing theme, and clicking "ok" results in Javascript error → cannot switch classic theme: changing and clicking OK gives an error on the Javascript console
QA Contact: sairuh → pmac
*** Bug 84043 has been marked as a duplicate of this bug. ***
*** Bug 85001 has been marked as a duplicate of this bug. ***
*** Bug 85156 has been marked as a duplicate of this bug. ***
10 dups. Adding mostfreq as some people still use that keyword.
Keywords: mostfreq
I've also looked into this before and agree with Ben -- something is getting trashed. Reassigning, guessing Ben probably meant to.
Assignee: ben → trudelle
Component: Preferences → XP Toolkit/Widgets
Keywords: nsbeta1+
QA Contact: pmac → aegis
Target Milestone: mozilla0.9.3 → ---
*** Bug 86188 has been marked as a duplicate of this bug. ***
*** Bug 86332 has been marked as a duplicate of this bug. ***
I was seeing this, but haven't in recent builds. Anyone else still seeing it on the trunk?
Yeah, it still occasionally happens to me after switching panes some.
I can reproduce in today's comm. trunk build on win2k (provided I can actually get the skin to switch, but that's a separate issue).
*** Bug 83419 has been marked as a duplicate of this bug. ***
pushing out past rtm, since onthefly skin switching is out for rtm.
Assignee: trudelle → hyatt
Target Milestone: --- → mozilla1.0
Ok, let me get this straight. NS6 comes and goes, andit's lauded as the buggest white elephant since MS Bob. One of the heralded features is the ability to change themes. So, now that 6.1 is being worked on, which is going to be 6.0, but done RIGHT, the PDT decided this ISN'T an RTM worthy feature? I can understand not feeling the presure to make this top priority, but I think it needs to be at LEAST cleaned up a bit. If "On The Fly" isn't an RTM feature, fine, but at least an interim fix should be a "please restart your app" message, and the OK button closing the Prefs window. I'm not one of the folks who whines and thinks everythign should be perfect, but the big things hsould at least work, if not doing everything wanted, functional without causing confusing behavior. Downgrading fron On The Fly switching to popping up a message is not dishonorable. Like I said, I think at least making it function reasonably is important. From an Netscape perspective, while the media is looking like they'll be forgiving about 6.0 if 6.1 lives up to it's potential, I don't think they're going to gloss over trying to change themes, and getting no response from the app. Has there been any progress of success in boiling down why the problem occurs? If it's not too heavily based in the machine code, but rather located in the XP portions of the app, I'd be willing to dive in and take a look around. My C skills are a tad rusty after [too many] years...
REOPEN+RESOLVE DUPE: *** This bug has been marked as a duplicate of 52441 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
argh. wrong bug. ignore that.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
May God have mercy on us all. The 212 bug spam-o-rama is Now!
QA Contact: aegis → jrgm
Status: REOPENED → ASSIGNED
Target Milestone: mozilla1.0 → mozilla1.0.1
*** Bug 111685 has been marked as a duplicate of this bug. ***
Sounds like this should be fixed by 127784. ->blaker
Assignee: hyatt → blaker
Status: ASSIGNED → NEW
Depends on: 127784
I get the feeling that this bug is no longer a problem. That is, the error no longer happens. Thoughts?
wfm
Status: NEW → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.