Earlier this year, all the major browsers released Cascade Layers, with the potential to fundamentally change how we write styles. But fundamental changes require us to re-think how all the pieces fit together.
All browsers add an
body element –
it’s part of the w3c-recommended
which browsers generally use
as a starting point
for their own ‘user agent’ styles.
Where does that come from?
Cascade layers are a new CSS feature that allows us to define explicit contained layers of specificity.
CSS Custom Properties (aka Cascading Variables) have gained broad browser support since 2015 – but what are they good for, and why do we need them?
How do we write code that is modular & maintainable, in a language designed to be systematic & contextual?
The Cascade makes CSS unique – forcing us to revisit even the most common programming feature: the variable.
From the very start, “web design” has posed a nearly impossible paradox.
Why waste your time on half-measures? Make your site THE MOST NORMALEST with this ULTIMATE CSS RESET.
There are a number of property & value combinations that can lead to CSS being inactive, and now Firefox will tell you why. Open the developer tools, and look for the greyed-out property with an info-box on hover.
The web is designed to work across platforms, devices, languages, and interfaces – but how can we possibly design for that unknown and always-changing canvas?
I’ve often used
unset in my CSS –
global keywords that can be applied to any property.
The difference is small, but important:
unset allows inheritance,
initial does not.
But then Firefox implemented
revert and I was confused –
how is this one different from the others?!
Love it or hate it, CSS is weird: not quite markup, not quite programming in the imperative sense, and nothing like the design programs we use for print. How did we get here?
From building beautiful sites to maintaining complex design systems across multiple applications, CSS is the web-language of design.