On Wed, Aug 6, 2008 at 2:04 PM, Daniel Friesen dan_the_man@telus.net wrote:
Splarka made a note about the [[MediaWiki:Print.css]] and [[User:Username/print.css]] proposals. A skin-skinname class would be useful to prevent the need for multiple of those, one for each skin.
I guess so, yes . . . is that the only one people can think of where there's no other nice way to do it? If it is, I think that MediaWiki:Skinname/print.css and MediaWiki:Common/print.css (or whatever) would be more consistent with how we currently do things.
I also note that it's useful for code that does belong in Common.css, but needs minor skin tweaks. That's actually especially useful if there are two or three skins that use similar locations or styles for that common code. Say css changes for message boxes inside of the content area, on skins that have a dark content area. You could put it in Skinname.css, but then you end up duplicating the code for each skin needing it, separating the code from the rest of the styling for those boxes, and also increasing the chances you'll forget to update the code for one of those skins.
You should just use cascading here. Put the bulk in Common.css, and put the actual color values (or whatever needs per-skin customization) in Skinname.css.