Quote:
Originally Posted by JSWolf
You don't need the text transform to uppercase. Just have the text already be uppercase. Also, it doesn't work in all cases. So it's better for compatibility to use <span>. You also don't need a .small class as <small> is already .9em.
|
That is actually the argument I made the last time we got in an argument about small-caps...I'm glad to see you got my point!
I actually wasn't trying to make an argument here for small-caps...I was making the argument for pseudo-selectors (the point of this thread). You said that they required 'ridiculously convoluted code'... I was just showing how simple and unconvoluted pseudo-selectors are. Please, don't get thrown off track by the example using small-caps; it could be ANY css used as a example.
Quote:
Originally Posted by JSWolf
But seriously, why do they need @media queries? At least one breaks in older RMSDK. And they are not needed anyway. Other then Kindle @media queries, I've never seen any in a novel other then from Standard eBooks.
|
I don't think anyone has mentioned media queries here?? We are talking about pseudo selectors...completely different.
Having said that, media queries started out as primarily a kindle thing, but now they can be used to get the screen size and orientation among other things. Definitely useful on any device that supports queries. Added to the functionality of @media is @supports...that way you can check to see if the device supports a css function before setting it. These two things could be considered 'more convoluted' than basic css...but they aren't really that bad once you get used to them. In any case, they should not be confused with the subject of pseudo-selectors.