I’ve joined the CSS Working Group as a W3C Invited Expert to help to
develop the next level of Cascading & Inheritance, in addition to other
CSS standards. I’m also currently active in the CSS4 and Design
Token Community Groups.
I was invited to join after the CSSWG approved work on my proposal for
extending the CSS Cascade & Inheritance module, so that authors can
define custom CSS origins. Jen Simmons presented the proposal at a
CSSWG “face-to-face” meeting, along with supporting slides. I’ll write
an article with details about the proposal soon.
I think it’s a brilliant idea.
Almost want to stop talking about whether or not to do it,
and just start talking syntax.
—Florian Rivoal, Invited ExpertatW3CCSSWG
In the meantime, it’s an honor to join the W3C, and help define the
future of a language I love. I have a lot to learn about the process,
but I’m excited to start contributing!
New CSS features are shipping at an unprecedented rate –
cascade layers, container queries, the :has() selector,
subgrid, nesting, and so much more.
It’s a good time to step back and understand
how these tools fit together in a declarative system –
a resilient cascade of styles.
What makes something a ‘grid’, and what’s at stake?
byMiriam Suzanneon
Back in 2020, Firefox released a prototype for doing ‘masonry’ layout in CSS. Now all the browsers are eager to ship something, but there’s a hot debate about the best syntax to use.
Over the last month, the CSS Working Group has determined we can loosen containment restrictions for query containers, and agreed on a syntax for special-case support queries (like support for the gap property in a flex context, or support for align-content in a block flow context).
