User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 A naked base firefox theme, A breakdown of files/images for those who want to pick up and make their own skin for firefox. This would very likely help weed out files that were removed from previous skin versions (ie: AboutDialog.css) and random, no longer-used/changed elements found in other files. Also giving someone with at least some mild skinning experience a breakdown of the current theming API and all functions available with an up to date theme.jar source tree along with good source documention to help them get on their way. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Provide the source 2. Package It 3. Let the user play Actual Results: Created a theme from scratch! Expected Results: Provided a naked theme.jar :) If something like this already exists out there, please feel free to point me to it. As I've searched and searched and found nothing. And most existing themes still contain files that have yet to get weeded out or accuratly updated but still work :)
The classic.jar in binary distros is the closest thing we have to this. If files are there that are no longer necessary, please file bugs so they would be removed. There are tutorials out there on how to use CSS to theme the various elements. There isn't an API as such, its just styling the XUL using CSS and defining images as appropriate.
(In reply to comment #1) > There are tutorials out there on how to use CSS to theme the various elements. > There isn't an API as such, its just styling the XUL using CSS and defining > images as appropriate. Well, that's what I meant, many of the tutorials I've encountered (perhaps I'm using the wrong search terms here and there) have appeared slightly outdated, and are still refferencing most of pre-rc1 changes without any mention of anything really significant. For example #233607 https://bugzilla.mozilla.org/show_bug.cgi?id=233607 . Many themes still contain some excess files that need to be weeded out and the default theme is using an internal structure of sorts and lacking some key installation rdf's to get a real sense of how to work it out. I'm guessing the classic.jar you mentioned is updated frequently enough to reflect changes in the nightlies, or enough so to get an idea between versions and directory structure as a stand-alone file. Just one you can install like any other theme, as I've noticed the under my profiles, in the single rdf for the theme it's marked as not being able to be uninstalled.
Assignee: bugs → firefox
Component: Extension/Theme Manager → General
QA Contact: bugs → general
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
this is more a theme extension than anything else. not for default FF but for a theme owner to make.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → INVALID
Yeah, I agree, this bug can be deleted. Originally what I had in mind was basically some nice breakdown straight from mozilla outlining what display options are open to tweaking via themes. I suppose it's burried somewhere on the wiki as I've had no luck finding anything thorough but it's not a big priority. However somewhere down the road, a nice documentation of all functions for themes/extensions and what's available to theme upon would be nice. XULplanet is a bit... well, it's damn dead.
You need to log in before you can comment on or make changes to this bug.