Closed Bug 64099 Opened 24 years ago Closed 24 years ago

switching themes makes it so I can't close the pref dialog

Categories

(Core Graveyard :: Skinability, defect)

Product:
Core Graveyard
Component:
Skinability
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: sspitzer, Assigned: bugs)

References

Details

launch "mozilla -mail", start in modern theme. Edit | Preferences | Appearance | Themes, apply "classic" now you're in classic. go to hit "OK", get this error: JavaScript error: chrome://communicator/content/pref/pref-fonts.js line 168: top has no properties JavaScript error: chrome://communicator/content/pref/pref-fonts.js line 168: top has no properties that prevents me from closing the prefs window. I have to use the window manager [X] to close the prefs dialog.
Regression of bug 40884?
This also occurs in today mac build. The pref dialog is hidden behind the browser window. I have to force quit. AT times I'm able to move the pref dialog(if I can see it) to make it active. macos commercial seamonkey build 2001-010210-mtrunk installed on G3/400 OS 9.04
Component: Preferences → Skinability
QA Contact: sairuh → blakeross
Hmm.. this is *very* annoying. I think this is a duplicate of bug 40884 because they both cause the same behaviour (although there are two ways to reproduce it). See my comments in there, and if you are interested in this bug. Please cc on bug 40884.
I see no comment from you on that bug, hwaara.. sspitzer do you still see this?
I'm crashing in nsCSSFrameConstructor::ConstructXULFrame() using a mozilla debug mac build pulled late this morning. We should at least look into this. Nominating nsbeta1
Keywords: nsbeta1
Actually, the crash I saw is bug 67726.
*** Bug 65167 has been marked as a duplicate of this bug. ***
Marking All/All
Severity: normal → major
OS: Linux → All
Hardware: PC → All
Blocks: 68973
Marking dogfood and nsbeta1- because I don't think Ben will get to this for beta1.
Keywords: nsbeta1 → dogfood, nsbeta1-
I must have done this several times, with several different builds on all three platforms in the past 10 days without hitting this bug (I do it as part of my setup for page tests). marking WFM.
Keywords: dogfood → nsdogfood
Umm, I think John forget to set the resolution to W4M. ;-)
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Er, um, yeah ... I meant to do that. Really.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.