Closed
Bug 59106
Opened 24 years ago
Closed 24 years ago
Crash if selected skin is no longer available
Categories
(Core Graveyard :: Skinability, defect, P3)
Tracking
(Not tracked)
People
(Reporter: Erich.Iseli, Assigned: hyatt)
Details
Before installing a new build, if you are using a skin else than classic or
modern, then install that new build, you can't load mozilla: it crashes on
startup. Because when you deleted the old build, you also deleted the chrome
directory and its installed chromes. However, in the user profile, there is
still some information about that no longer existing chrome.
Reporter | ||
Comment 1•24 years ago
|
||
I forgot to mention a suggestion: If the needed chrome is not available, instead
of making mozilla crash, it should use the default chrome (modern or classic,
which are always installed).
![]() |
||
Comment 4•24 years ago
|
||
Dup of that bug 53670 which has been marked future and WONTFIX.
Fabian. (wonders why this hasn't been marked a dup before)
*** This bug has been marked as a duplicate of 53670 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified dupe of wontfix bug 53670: "New build won't start if 3rd party theme is
used in old build [@ nsCSSFrameConstructor::ConstructDocElementFrame]"
Status: RESOLVED → VERIFIED
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•