Help talk:CSS

'Additionally, the square light blue bullets cannot be changed.' Pretty sure .pBody ul {list-style-image:url(url);} will do that.

Also, I think it might make sense to have the properties list as a table, for easier reference; and I realise this isn't meant to be a complete resource of any kind, but a lot of what are, IMO, quite important properties are missing. For example, display, width, height, position with top/right/bottom/left, float. And for font-weight, it could do with stating that for all purposes, only normal and bold are really distinguishable from the values.

Furthermore, the 'Advanced' section isn't so much advanced as just introducing a couple of wiki-specific selectors; it could do with something like advanced selectors (+, >, *, selecting elements with HTML attributes via [attribute="value"], pseudo-elements) if it need exist at all. Also, compound selectors are used in places but never explained; that could go here.

And about measurements: em is missed out when talking about font sizes, where it's pretty important, and it could be stated how px/em/% differ when used for sizes other than fonts. Finally, I think that the page could do with either a list of useful classes and ids on the wiki, or instructions as to how to derive them by looking at the HTML.

If the page doesn't need to have all this, then maybe it should link to a full CSS tutorial/reference elsewhere, describing this page as only a starting point.

Thanks to anyone who takes the time to read this, and I'll gladly help sorting all this out if anyone thinks it's a good idea.Greenpickle

This was something I did a very long time ago, hoping others would enjoy doing skins as much as I do. But I am the only active person who creates a complex skin semiannually, there are a few others who do it a little bit when they want to. Since I did this I have learned that bullets can be changed, and since it wasn't a critical page, I haven't really updated it. I do believe that width, height, position and float are things that should not be changed in a wiki software site, as I tried once to extent the area content to take over the new space created by deleting the ads, but it completely offset several other settings in other core wiki functions. So, I leave those alone. I do think an external page (w3schools is excellent) resource link would be good, feel free to fix up this page however you like. Wa _T^C_@^Y 16:01, 4 March 2009 (EST)

I've made quite a lot of changes, mostly tidying the lists up into tables, adding an expanded section about selectors, and adding more properties and selectors to the lists. I wasn't really sure how much to include, so I left out quite a few points, and selectors and properties that aren't really important or used much. Concerning width/height/position/float, they can be used just fine on a wiki, even for the largest elements on the page, it's just hard to understand what exactly they do and takes some experimentation (which is much quicker if you're using something like Firebug). It is often a lot easier to work with margins to space things instead, though, I guess.Greenpickle

Hey, is there a way to customize what happens to items on the watchlist if they've been edited since your last visit? Because right now they use strong tags, which the DSi doesn't understand. - 2257^(Talk) 12:06, 10 April 2009 (EDT)

Nevermind, I figured it out. Is there a way to make it apply to only the DSi? - 2257^(Talk) 12:22, 10 April 2009 (EDT)

Well, I thought I could do it with @media handheld{strong a {/*Customization goes here lol*/}} but that doesn't seem to work, so I'm lost. The DSi responds to @media screen{strong a {/*Customization goes here lol*/}} Which is unfortunate, because that's supposed to be reserved for computers. Or did I do something wrong? - 2257^(Talk) 16:53, 10 April 2009 (EDT)