Bugzilla CSS plan

Maxwell Kanat-Alexander mkanat at kerio.com
Tue Jul 27 18:36:17 UTC 2004


On Fri, 2004-07-23 at 19:36, Christian Robottom Reis wrote:
> > 	Oh, a fine idea. What would be against having a custom stylesheet for
> > the page-specific ones, as well? They'll be empty files, the worst that
> > will happen is extra hits on Apache.
> 
> I claim YAGNI -- overriding page-specific CSS can be done in custom.css
> and that's enough for most purposes; full-blown skins can replace more
> files if they like, but won't have the cvs-update-protection that
> custom.css gets.

	Huh... I'm very wary of saying YAGNI when it comes to extensibility of
Bugzilla. From what I've seen, everybody's favorite thing to do is
customize Bugzilla as soon as they get their hands on it.

	However, I can't yet imagine a problem with custom.css being the only
custom file.

	Anyhow, what I'd really want do as a Bugzilla admin is modify the
shipped CSS files, and then add a bit of custom CSS. I wouldn't just
modify the custom.css. 

	I suppose that's the value of the "skin" idea -- it lets me modify a
different set of the original files, but keep the real originals in case
I want to look at them or use them again for bug fixes.

	-Max





More information about the developers mailing list