User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 An idea that would help improve the theming system is the concept of a master theme. This would allow third party themes to include only the css/images relevant to that skin and have the program fall back to the master theme for elements not included. Conversely, updates to the master theme would be picked up when using third party themes. Opera’s theme system currently works this way. This greatly reduces the complexity of third party themes by eliminating the need to package the entire UI. Additionally, it reduces the chances of themes becoming incompatible due to UI changes, as was the case with the scrollbar binding change around 0.8, and the Find Toolbar in 1.0 PR. Reproducible: Always Steps to Reproduce:
*** Bug 277716 has been marked as a duplicate of this bug. ***
Definitely something I'd like to see for 1.2
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Theming system should use a master theme as a fall back → Allow theme inheriting
Uhh, userChrome.css? Partly joking. What you're asking for is already entirely available via userChrome.css. Not sure i completely agree with the "master theme" concept, but definitely think there should be theming standards (common CSS classes, perhaps common filenames/locations, etc.) that should be followed, both for consistency throughout the default theme and for ease of third-party themers.
You need to log in before you can comment on or make changes to this bug.