Jump to navigation
Jump to search
Notmyhandle (talk | contribs) (→Skins: additionally...) |
(→Skins: Reply) |
||
| Line 90: | Line 90: | ||
Hey Ech, I was trying to update my reskin of bluecloud but I ran into a little problem. I'm attempting to alter the background of the gallery that appears in image categories (I assume this is the same as using <nowiki><gallery></nowiki>) to black, but to no avail. I've changed all the references I believe that would be handling that attribute, but still nothing. Using WebDeveloper I've looked into what inherited values could be causing the problem, and all I can pinpoint are from http://media.strategywiki.org/w/skins/common/commonPrint.css (what is that anyways? could it be globally dominating all the skins?). I dunno, maybe I'll go back and keep looking for substitutes, however, I had the idea that maybe we could create an actual entry for the skin so that it wouldn't have the inherited bluecloud css possibly messing it up. Could we do that? --{{User:Notmyhandle/Sig}} 02:46, 5 November 2007 (CST) | Hey Ech, I was trying to update my reskin of bluecloud but I ran into a little problem. I'm attempting to alter the background of the gallery that appears in image categories (I assume this is the same as using <nowiki><gallery></nowiki>) to black, but to no avail. I've changed all the references I believe that would be handling that attribute, but still nothing. Using WebDeveloper I've looked into what inherited values could be causing the problem, and all I can pinpoint are from http://media.strategywiki.org/w/skins/common/commonPrint.css (what is that anyways? could it be globally dominating all the skins?). I dunno, maybe I'll go back and keep looking for substitutes, however, I had the idea that maybe we could create an actual entry for the skin so that it wouldn't have the inherited bluecloud css possibly messing it up. Could we do that? --{{User:Notmyhandle/Sig}} 02:46, 5 November 2007 (CST) | ||
:Additionally, we need to set up a policy (this is more like something we'll put up in community issues) about keeping templates, tables, etc. skin neutral. For instance, we need to define properties within specialized classes, otherwise skins like mine end up with a lot of contrasting colors of both extremes (dark blue on black, white on white, etc.). Although this increases the amount of data stored in each skin, it does have some reduction in data otherwise (substing a template with skin neutral properties will result in less characters being saved). I don't see it as a problem, but I'm not running the server nor do I have experience with MediaWiki. What do you think? --{{User:Notmyhandle/Sig}} 06:33, 12 November 2007 (CST) | :Additionally, we need to set up a policy (this is more like something we'll put up in community issues) about keeping templates, tables, etc. skin neutral. For instance, we need to define properties within specialized classes, otherwise skins like mine end up with a lot of contrasting colors of both extremes (dark blue on black, white on white, etc.). Although this increases the amount of data stored in each skin, it does have some reduction in data otherwise (substing a template with skin neutral properties will result in less characters being saved). I don't see it as a problem, but I'm not running the server nor do I have experience with MediaWiki. What do you think? --{{User:Notmyhandle/Sig}} 06:33, 12 November 2007 (CST) | ||
:: We already have a semi-official policy on this, and I've been moving the CSS out of templates wherever I see it in the wrong place. What you've done with the thankyou template isn't right though. You should add the class, and then move the CSS to [[MediaWiki:Common.css]], or better yet, notify me and I'll do it. --[[User:DrBob|DrBob]] ([[User_talk:DrBob|talk]]) 10:55, 12 November 2007 (CST) | |||