49822 - using classic skin makes browser not work

Status: VERIFIED FIXED

(SeaMonkey :: Themes, defect, P1)

Description

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

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.

Comment 1

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

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.

Comment 2

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Marking dogfood instead.

Comment 3

[Blake Ross]

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

Comment 4

[johng]

nav triage team:
nsbeta3+, P1

Comment 5

[Ben Goodger (use ben at mozilla dot org for email)]

hyatt sez he fixed this. 

Comment 6

[Asa Dotzler [:asa]]

this is fixed in 09/01 mozilla builds on win32NT, macOS9 and RedHat6.2