Closed
Bug 49822
Opened 24 years ago
Closed 24 years ago
using classic skin makes browser not work
Categories
(SeaMonkey :: Themes, defect, P1)
SeaMonkey
Themes
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: dbaron, Assigned: bugs)
Details
(Keywords: regression, Whiteboard: [nsbeta3+])
DESCRIPTION: Using the classic skin makes the browser not work. By this I mean: * crash when closing a window * crash when clicking a link * give a JS error on startup: JavaScript error: chrome://navigator/content/navigator.js line 399: window._content has no properties STEPS TO REPRODUCE: * load profile manager * create fresh profile * start mozilla * in prefs, switch to classic skin * exit * start browser again. Interestingly, my existing profile (which used classic skin) worked the first time I ran with it, and then showed these symptoms the second time.
Reporter | ||
Updated•24 years ago
|
Keywords: regression,
smoketest
Reporter | ||
Comment 1•24 years ago
|
||
A few more details: I'm testing on a Linux optimized build from tree closure today. tor also sees this bug. Changing back to the modern skin on my existing profile makes it work again. I put this on the blocker list so people are aware of it. I'm not sure if it should be there or not. Feel free to remove if it shouldn't be.
Reporter | ||
Comment 2•24 years ago
|
||
Marking dogfood instead.
Comment 3•24 years ago
|
||
I just saw this once upon starting up a new build using an old profile set to Classic, but couldn't reproduce it in subsequent attempts (loaded fine after the first time). ->themes, ben
Assignee: asa → ben
Component: Browser-General → Themes
OS: Linux → All
Hardware: PC → All
nav triage team: nsbeta3+, P1
Assignee | ||
Comment 5•24 years ago
|
||
hyatt sez he fixed this.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 6•24 years ago
|
||
this is fixed in 09/01 mozilla builds on win32NT, macOS9 and RedHat6.2
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•