Bugzilla CSS plan

[Gervase Markham]

Myk Melez wrote:
> To fix that, we should put customizations into skins/<name>/custom/.  
> This makes customizations skin-specific, but I think that's actually 
> what we want, since customizations to the standard skin are unlikely to 
> apply to any random skin an installation installs.

Sounds good.

> We currently give body tags a domain-specific ID.  We should make that a 
> class and give them page-specific IDs instead or make them both classes, 
> probably the latter.

Do any major browsers have problems with this sort of multiclassing? If 
so, I'd suggest that body tags get a domain-specific class, and a 
page-specific ID. And we should do that on the 2.18 branch so we don't 
do a major release with a deprecated scheme.

>> Could this mechanism be combined with the multiple skins thing above? 
>> For example, the Param could instead give a list of permitted 
>> alternative skins, with the first one being the default.
> 
> I want admins to be able to add a skin to their installation just by 
> dropping it into the skins/ directory.  Ideally the parameter would 
> dynamically populate its list with the contents of skins/, but I'll 
> settle for a text field if that's not possible.

My suggestion matches localisations almost exactly, FWIW. For 
localisations, you drop the templates in and change the "languages" 
param to add the new language name. For skins, you would drop the skin 
in and change the "skins" param to add the new skin name.

Gerv