4 ms·
In my experience, very, very few Web designers actually use specificity (UPDATE: I should have added "properly," as was pointed out). It works extremely well,
by ChrisMarshallNY 7y ago
In my experience, very, very few Web designers actually use specificity (UPDATE: I should have added "properly," as was pointed out).
It works extremely well, if everyone follows the rules, which is uncommon.
That goes for most of CSS; not just specificity.
CSS is incredibly powerful, if used properly, and specificity, when actually used properly, is very cool.
About ten years ago, I wrote this series: https://littlegreenviper.com/miscellany/stylist/introduction-to-specificity/ https://littlegreenviper.com/miscellany/stylist/introduction...
It’s still absolutely relevant nowadays, and just as few people follow that workflow now, as they did then.
CSS, in general, is too complicated (IMNSHO), but that complexity is also what makes it so powerful.
I’ve always enjoyed Stu Nicholls’ CSSPlay site, for examples of extreme CSS: http://www.cssplay.co.uk/menu/ http://www.cssplay.co.uk/menu/
- tiborsaas 7y agoI find this really hard to believe. Specificity is baked into CSS at such a fundamental level that you can't not use it. Maybe you meant like they don't use it consciously of effectively?
- ChrisMarshallNY 7y agoFair ‘nuff. People don’t use it consciously, so my statement was not specific enough. :)
- ZenPsycho 7y agothere’s using it deliberately as a tool, and running into it unexpectedly and doing absurd things to work around it like it’s an obstacle to overcome. i see much more of the latter than the former; squarely i think because most css is written by people who don’t know how to use specificity - so they come up with things like BEM, or css in js frameworks to force specificity away like it’s a flaw in the system. all this work goes in because module scope is an easier mental model to grasp than specificity, which i suppose works more like traits. but, having been in this web making game long enough, it seems like a return to table based design and font tags. just with different syntax.
- ChrisMarshallNY 7y agoPeople have been freaking out about table-based design for twenty years. It’s a great foil, and much of the criticism is merited, but it’s not the end of the world. You can fairly easily turn tables into blocks: https://littlegreenviper.com/miscellany/stylist/another-reason-to-use-table-based-layout/#dont-tell-mom https://littlegreenviper.com/miscellany/stylist/another-reas... Also, I use “display: table” all the time in my work. It’s the best mode for layout that fits content.
- ZenPsycho 7y agoyou’re kind of missing my point. which is fine because i didn’t spend a whole lot of words explaining it. i am not saying table based design is bad. but we did originally move away from it for legitimate reasons that seem to have been largely forgotten, and as a result we now have developers who build json theme files and react frameworks that wire “darkmode=true” individually through every component instead of just using css for what it was designed to do: to exactly be a theme configuration format. a lot of where things have gone wrong is CSS started to be used for layout, which was originally a hack, abusing the float property to do things it was never designed to do. and css has never gotten good at it, because fundamentally layout is about relationships between elements, while CSS is stuck only ever specifying properties ON elements. sure we have display table, flexbox and css grid, but css is an incredibly awkward and unnatural way to express those concepts. app frameworks deal with layout seperately from colors and fonts, which is how it should be done. and so this is why it’s all hacks and workarounds in css land. it doesn’t have to be this way. but it’s how it is.
- ChrisMarshallNY 7y agoI got the point, but I found it a convenient coat hook for my favorite ulster :). I can certainly agree with you. Some of the dynamically-generated markup can be a nightmare. "ZenPsycho." Great screen name.
- orange8 7y ago> a lot of where things have gone wrong is CSS started to be used for layout The layout is part and parcel of the style. CSS gives you 7 different layout modes to choose from (normal, table, float, positioned, multi-column, flex and grid). There is more than enough here to implement any sort of layout problem you face, from using 15 year old table and flex hacks to cleaner modern approaches like flex. > while CSS is stuck only ever specifying properties ON elements The "position: relative" (CSS1), float and flex are all about positioning elements relative to one another. Other properties like margin, align and float are also about positioning items relative to one another. > but css is an incredibly awkward and unnatural way to express those concepts I think CSS is pretty easy and straightforward to reason about, once you decide that it is worth investing some time and effort in learning. It really always surprises me how some really smart people just do not get CSS, and I think it is not about ability, but attitude. CSS is dismissed as "that thing for designers", and calling CSS a programming language is usually met with smirks. That is the real problem with CSS, its reputation.
- ChrisMarshallNY 7y agoOne of my rules of thumb, is that “!important is FAIL.” If I find that I need to use the !important modifier, I’m usually being lazy. Where I do tend to use it, is in print media styles, to force a style over CMS themes, which can be notoriously bad (for example, one of the themes I have used spews out multiple duplicate #ids. When I reported the bug, the response was basically “shrug Sucks to be you.” That was the least of the issues with the theme, and I was forced to use !important a few times).
- jt2190 7y agoNot the OP, but what I commonly see are elaborate behaviors by devs to try and avoid dealing with specificity head-on, because it’s so hard to reason about. In my opinion this leads to CSS that is two to three times longer than strictly necessary. That said, I also believe that CSS was the wrong solution to the wrong job: CSS addresses the DOM, not the UI, and does so with a kind of “multiple inheritance by default” approach, where an element will inherit properties via the cascade from many rules, until a rule that stops the cascade is written. Reasoning about what rules apply to what elements under what conditions becomes an exercise in extreme abstract thinking, and still there is another step to think about what the resulting UI that it will generate will look like. (I’ll leave off browser differences for now.)
- ChrisMarshallNY 7y agoThankfully, browser differences are reducing to a point near zero, for most "classic" CSS issues. They still have lots of differences in the way they interpret JS, though, as well as some of the newer CSS rules. I've learned that if I keep my markup and style to "early" CSS3/HTML5, I can create pages that render pretty much the same on all browsers. It's when I try to get fancy, that things go pear-shaped. That said, check out CSSPlay (http://www.cssplay.co.uk/menu/ http://www.cssplay.co.uk/menu/). He's been pulling off extreme CSS acrobatics since CSS 1. Amazing stuff.