Steve wrote:
> Oops. The other constant between my 3 machines would be my use of
> "graymodern" as a new theme. If I quit a particular Mozilla in this
> theme and then restart it with a different Mozilla build without that
> theme, the app freezes.
>
> Conversely, if I shift that particular Mozilla back to one of the
> default themes before quitting, quit, and then open a different build
> of Mozilla, everything's fine.
>
> Anybody know why this happens? Kind of a pain in the butt to install
> new themes when I download new browser builds. Can you treat themes
> like mail or some sort of independent preference to avoid this problem?
>
> Steve
>
It happens because Mozilla fails to go to a default theme if it can't find
the theme listed in chrome/user-skins.rdf in your profile. I reported this
bug in September.
See http://bugzilla.mozilla.org/show_bug.cgi?id=53670 for details.
When Theme writers use a xpi installer it places the theme in
chrome/skins/themename. Since it only exists in the copy of Mozilla you
installed the theme into Mozilla can't find it if you upgrade, use a
different copy of Mozilla, or use Netscape 6. If the theme writer uses the
jar format the theme can be loaded into the profile where Mozilla can allways
find it.
You can convert your favorite theme to jar format with the Themewrap tool, or
set up a seprate profile that's used to load new copies of Mozilla, keep it
set to Classic or Modern.
John Dobbins
