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)
Core
XUL
Tracking
()
RESOLVED
WORKSFORME
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).
Comment 2•24 years ago
|
||
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
Comment 5•24 years ago
|
||
->all, since it happens on linux and win32 [see dups].
nav triage team:
Reassigning to Ben.
Ben, can you look into this and tell us if it's a beta stopper
Assignee: mcafee → ben
Updated•24 years ago
|
Priority: -- → P2
Target Milestone: --- → mozilla0.9.2
Comment 7•24 years ago
|
||
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.
Comment 8•24 years ago
|
||
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
Updated•24 years ago
|
Comment 10•24 years ago
|
||
*** Bug 80218 has been marked as a duplicate of this bug. ***
Comment 11•24 years ago
|
||
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
Updated•24 years ago
|
QA Contact: sairuh → pmac
Comment 12•24 years ago
|
||
*** Bug 84043 has been marked as a duplicate of this bug. ***
Comment 13•24 years ago
|
||
*** Bug 85001 has been marked as a duplicate of this bug. ***
![]() |
||
Comment 14•24 years ago
|
||
*** Bug 85156 has been marked as a duplicate of this bug. ***
Comment 15•24 years ago
|
||
10 dups. Adding mostfreq as some people still use that keyword.
Keywords: mostfreq
Assignee | ||
Comment 16•24 years ago
|
||
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 → ---
![]() |
||
Comment 17•24 years ago
|
||
*** Bug 86188 has been marked as a duplicate of this bug. ***
Comment 18•24 years ago
|
||
*** Bug 86332 has been marked as a duplicate of this bug. ***
Comment 19•24 years ago
|
||
I was seeing this, but haven't in recent builds. Anyone else still seeing it on
the trunk?
Comment 20•24 years ago
|
||
Yeah, it still occasionally happens to me after switching panes some.
Comment 21•24 years ago
|
||
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).
Comment 22•24 years ago
|
||
*** Bug 83419 has been marked as a duplicate of this bug. ***
Comment 23•24 years ago
|
||
pushing out past rtm, since onthefly skin switching is out for rtm.
Assignee: trudelle → hyatt
Target Milestone: --- → mozilla1.0
Comment 24•24 years ago
|
||
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...
Comment 25•24 years ago
|
||
REOPEN+RESOLVE DUPE:
*** This bug has been marked as a duplicate of 52441 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Comment 26•24 years ago
|
||
argh. wrong bug. ignore that.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 27•24 years ago
|
||
May God have mercy on us all. The 212 bug spam-o-rama is Now!
QA Contact: aegis → jrgm
Updated•23 years ago
|
Status: REOPENED → ASSIGNED
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 28•23 years ago
|
||
*** Bug 111685 has been marked as a duplicate of this bug. ***
Comment 29•23 years ago
|
||
Sounds like this should be fixed by 127784. ->blaker
Comment 30•23 years ago
|
||
I get the feeling that this bug is no longer a problem. That is, the error no
longer happens. Thoughts?
Comment 31•23 years ago
|
||
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.
Description
•