- CSS selectors allows to point to elements on the page to style them
- we have dozens of pseudo classes available to style element
:target
allows us to do lightboxes without JavaScript:not
reverses the meaning of the symbol selector inside it:not([class])
allows you to style elements without classes, without specificity wars- adding the letter i to attribute selectors allow you select them without case sensitively
- there is nothing new is CSS selectors. Why? As devs we are not asking for them.
- developers have started styling everything with class selectors
- we’ve abandoned HTML semantics
- As developers, we have started put a bird on it people
Put a class on it
-developers
- our over-reliance on classes is modifying the spec
:local-link
is not supported- the reference combinator is not supported
- both of these cool features have been dropped the selector spec
- the
:has
selector lives but comes with fine print, it only works in JavaScript - decisions are being made without the developers voice (not to say wrong, just our voice is absence)
- The labotomised owl selector,
* + *
, has zero specificity. It makes it easy to override it. - Quantity selectors allow us to code defensively against changes in the content structure within a CMS
- demand the selectors we deserve in future browsers
Leave a Reply