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 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. If you read the bugzilla entry you'll notice another issue with the commit. I didn't notice it till after, but all that was added was a lazy get_class( $this ); which is an unreliable way to get the name of the skin, we have member variables for that. I have doubts about if the code actually worked right. ~Daniel Friesen(Dantman, Nadir-Seen-Fire) of: -The Nadir-Point Group (http://nadir-point.com) --It's Wiki-Tools subgroup (http://wiki-tools.com) --The ElectronicMe project (http://electronic-me.org) --Games-G.P.S. (http://ggps.org) -And Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG) --Animepedia (http://anime.wikia.com) --Narutopedia (http://naruto.wikia.com) Chad wrote: