65530 - fallback to global default chrome if user choice not found

Status: VERIFIED DUPLICATE of bug 53670

(Core Graveyard :: Skinability, defect)

Description

[Daniel Veditz [:dveditz]]

From the newsgroups: User has two Mozilla installations (one is actually 
ActiveState's Komodo), has downloaded a global skin from x.themes.org into one 
of them, and selected that theme in his profile. When he switches to the other 
Mozilla (without the chosen theme) it will not start at all.

If we can't find the skin referenced in the profile "user-skin.rdf" we should 
fallback to the global "user-skin.rdf" for the default which must exist unless 
the installation has been mucked with.

Ditto for locales.

Comment 1

[R.K.Aa.]

isn't this in effect a dup of bug 53670:

New build won't start if 3rd party theme is used in old build [@
nsCSSFrameConstructor::ConstructDocElementFrame]

Comment 2

[Fabian Guisset]

It's a dup, but I'd like to keep this bug open. Hyatt/Ben say this would never
work in  bug 53670, but we can do a last attempt ;)

Comment 3

[Keyser Sose]

The other bug is reopened marking this as a duplicate of it.

*** This bug has been marked as a duplicate of 53670 ***

Comment 4

[Diego]

Verified dupe of reopened bug 53670: "New build won't start if 3rd party theme
is used in old build [@ nsCSSFrameConstructor::ConstructDocElementFrame]"