Closed
Bug 142445
Opened 24 years ago
Closed 24 years ago
Themes won't be applied
Categories
(SeaMonkey :: Themes, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 134039
People
(Reporter: asbjorn, Assigned: shliang)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc1)
Gecko/20020417
BuildID: 2002041711
Whenever I try to apply another theme than the standard default 'classic', it
just won't. I get no error message, but there's a difference between v1.0 RC1
and earlier versions in that now you have to restart the browser for the skin to
get applied. That's wierd, and not an improvement imho.
I haven't yet restarted my computer after the installation (nor did the
installation tell me to), but the bug might go away when I do. Though should you
probably know about it, so you can fix it in later versions. :)
Best regards,
Asbjørn Ulsberg
asbjorn@tigerstaden.no
Reproducible: Always
Steps to Reproduce:
1. Try to apply a theme
2. The theme doesn't get applied, even when the browser is restarted (which you
didn't have to do in earlier versions).
Actual Results: The theme doesn't get applied to the browser.
Expected Results: Mozilla should have applied the theme, of course. ;)
Comment 1•24 years ago
|
||
Do you use quicklaunch ?
Have you installed the correct skin version (a working RC1 Skin) ?
Comment 2•24 years ago
|
||
via email :
Yes. I researched a bit, and found out that when I disabled
quicklaunch (or restarted it) and then restarted Mozilla after
changing theme, the theme did infact change.
So it seems that the quicklaunch "holds on" to the preferencenses,
hence also the theme-selection. A bug or not, this should be
corrected somehow and some day.
The best thing would be if the theme changed instantly, the second
you chose a new one.
Thanks for your answer !
*** This bug has been marked as a duplicate of 134039 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•18 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•