![]() ![]() The idea (I suppose) is it kinda acts like currentColor except for any property. PPK has a fifth value he thinks would be useful: cascade. If we had that, we’d have a very powerful tool for starting fresh with styles on any given element. We have four properties for fiddling with the cascade on individual properties, but none that allow us to blast everything back to the UA stylesheet defaults. ![]() This keyword would be actually useful.Īmen. It reverts to the browser style sheet in all cases, even for inherited properties. I’m glad he found my whining about all this:Ĭhris Coyier argues we need a new value which he calls default. Kinnnnnda useful in that reverting display, for example, won’t make a element display: inline but it will remain a sensible display: block. But for non-inherited properties it means to revert to the UA stylesheet. Same deal for inherited properties, it means inherit. That’s a brain twister for me such that I’ve never used it. color) it means inherit, and for a property that isn’t inherited (e.g. initial will reset the property back to the spec default.That’s a decent and elegant way to handle the fact that you want the text and links in the footer to be the same color without having to set it twice. You might see that with an override of a link color, for example. Perhaps because it’s been around the longest (I think?) but also because it makes logical sense (“please inherit your value from the next parent up that sets it”). Of those, day to day, I’d say I see the inherit used the most. There are four keywords that are valid values for any CSS property (see the title). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |