Closed
Bug 170015
Opened 23 years ago
Closed 23 years ago
Mozilla 1.0 themes dont work for 1.2
Categories
(SeaMonkey :: Themes, defect)
SeaMonkey
Themes
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: codyrl, Assigned: shliang)
References
()
Details
I've noticed since .9.x whenever it moves over to a build number (ie .9.6 to
.9.7) themes for the previous build WILL NOT work on the current build, this
seems to be the case for Mozilla 1.0 themes on Mozilla 1.2 beta, there needs to
be a way for 1.0x builds to be compatible with 1.2x so that there wouldn't have
to be re-writes of a theme in order to get it to work on 1.2
Comment 1•23 years ago
|
||
I was just talking to him about that. IT happened on mine too.
Comment 2•23 years ago
|
||
This is normal. New GUI elements are introduced in some major versions
of Mozilla, and themes for previous versions of Mozilla don't have XUL
or icons for the new elements.
But should there be an automated way to convert 1.0 themes to an approximate
1.2 theme, perhaps by bringing in Modern icons to fill the gaps?
I usually use the pinball theme. It worked in 1.0 and 1.1. Mozilla should
probably detect that they are incompatible and not let me try to set them. Or
at least notify me when I relaunch the browser that I tried to use an
incompatible theme.
This also caused problems with quicklaunch.
it does detect it, but it would be nice to see a theme to be 100% compatible
from 1.0 - 1.99, so that the coders wont have to re-code the themes every few
weeks, and people with dialup connections wont have to re-download the same
theme over and over whenever a new version of mozilla comes out
Comment 5•23 years ago
|
||
would be nice, but that would mean adding nothing new to the interface, which
means no new features. that is the goal of the 1.0 branch - 1.0 themes will
remain compatible with 1.0.1, 1.0.2, 1.0.3, etc...
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•