Bugzilla Skins Code Probably Go

Skins can be either single CSS files (skins.css) or directories of files (skins ) with the same directoryfile structure as the default skin.

Note: This is not the place to request configuration, permission, or account changes to this installation of Bugzilla (bugzilla.mozilla.org).

File such changes under the appropriate component in the bugzilla.mozilla.org product.

This includes both presentation (how it looks) and behavior (how it works) but not functionality (what it does), which should be filed in a function-specific component like Email Notifications or in Bugzilla-General.

Examples of bugs you might file here include column label Pri is confusing and take anonymous users to the simple query page by default but not need way to filter for requests with no requestee.

Bugzilla Skins Code Probably Go

As a general rule, bugs that affect only a single Bugzilla web page or can be fixed with changes just to templates probably go in this component, while bugs that affect multiple pages or fixes to Perl code probably go somewhere else.

Build Identifier: Mozilla5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko20051111 Firefox1.5.

Currently there are many things that cannot be styled because we are single skinned.

Adding a second skin would help us keep an eye on styleability.

Bugzilla only ships with the standard skin and a custom directory for tweeking the standard.

Maintain 2 so that its obvious how well the skins are working.

Might be useful to spur further development in this direction.

Ill attach a global.css file which is almost exactly the one from bug 259723.

The patch here contains some changes of bug 264511 to make the bug 259723 skin work in a basic way.

Even without an additional skin directory, you can select whether to use the CSS files in the custom directory or not (by default you do).

That way admins can set a default, and users can pick whichever one they prefer for themselves.

Probably better to just use the hex notation and add a comment next to it saying that its lightgreen.

And I think that this is an r- on the way the param works, although I havent looked at the patch in too much depth.

There are id and class attributes missing all over the place.

And theres probably more trouble we arent currently aware of.

I think what we should do with this bug is add skinning in a semi-hidden way, along the lines of the implementation proposed here.

Rationale: dont have people start ripping us apart for skins and skinability deficiencies.) I can fix the CSS remarks for an initial checkin, and I can add a UI params category, too.

We can then, perhaps during the course of a release cycle, consolidate the three things that need to work together: Bugzilla HTML, the standard Bugzilla skin, and the secondary Bugzilla skin.

When were feeling good about this, we alter the param behaviour (and placing), and we add a user pref for skin selection.

We need to find a way to give credit to Mike who set up the skin.

Installation admins can install third-party skins by adding them to the skins directory and then adding their name to the skins parameter.