CSS Custom Properties Fail Without Fallback · Matthias Ott – User Experience Designer
Matthias has a good solution for dealing with the behaviour of CSS custom properties I wrote about: first set your custom properties with the fallback and then use feature queries (@supports
) to override those values.
Responses
Related links
una.im | Updates to the customizable select API
It’s great to see the evolution of HTML happening in response to real use-cases—the turbo-charging of the select
element just gets better and better!
Your CSS reset should be layered
This makes sense:
Wrap everything in your CSS reset with a
@layer
rule.When you place any styles inside a layer, these styles automatically have lower priority compared to all unlayered styles on the page. Think of it like an
!unimportant
block. You don’t need to worry about specificity or order of stylesheets at all.
My Modern CSS Reset | jakelazaroff.com
I like the approach here: logical properties and sensible default type and spacing.
Can you feel the rhythm‽ · 13 March 2024
Adam makes a very good point here: the term “vertical rhythm” is quite chauvanistic, unconciously defaulting to top-to-bottom writing modes; the term “logical rhythm” is more universal (and scalable).
Related posts
Displaying HTML web components
You might want to use `display: contents` …maybe.
Who knows?
Had you heard of these bits of CSS? Me too/neither!
Supporting logical properties
Using the CSS trinity of feature queries, logical properties, and unset.
Let’s get logical
Let me hear your blocky talk.
Faulty logic
CSS logical properties here, they just aren’t evenly distributed yet.
1 Like
# Liked by Matthias Ott on Saturday, June 13th, 2020 at 3:49pm