Closed Bug 186373 Opened 22 years ago Closed 22 years ago

themes backward compatibility

Categories

(Core Graveyard :: Skinability, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: uamjet602, Assigned: andreww)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 Themes for mozilla 1.0 don't work in mozilla 1.2 Reproducible: Always Steps to Reproduce: 1. Download a skin for mozilla 1.0 with mozilla 1.2 2. switch to it 3. Actual Results: Doesn't work Expected Results: Should work, as 1.0 to 1.2 is not a major version increment. I realize that there is already a bug with the same subject, but it is about wether mozilla should automatically fix/uninstall the theme. I realize that it might be a lot of effort. However, you cannot expect people to create a theme, which also requires a lot of effort, when the working life expectance is about a few months, as that is when it will be incompatible again. It is nice that there is a version inside the theme so mozilla can see that it is not compatible, but that version really should not increase unless there is a major new version (like mozilla 2).
You mean that the UI of Mozilla shouldn't change until 2.0? and what happens to new elements like the junk mail controls for example?
Suggesting invalid. New features means new UI and hence new skins. Should we wait until 2.0 for junk mail filters just because skins will be broken? Clearly not. If you want to use a 1.0 featureset and skin, use 1.0. Otherwise, use the later releases and be prepared to fall back to modern/classic. Also note that many skin authors do take the time and effort to update their skins. In addition, I believe you are entitled under MPL to take a skin you like and make the improvements yourself, should you choose.
Why not use elements from a standart (modern/classic) theme if the element is not present in the used theme.
-> Invalid That would mean that we can#t change anything between now and 2.0
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
v
Status: RESOLVED → VERIFIED
QA Contact: pmac → gbush
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.