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!
For many years, it has been ‘best practice’ to use relative units (especially em and rem) for sizing text. That’s great! But after playing around with my user preferences, I think we can improve on the common approaches.
It is frustrating to track down why an anchor isn’t being found. I’ve found a simple way that should work in most cases. If that doesn’t work, step through the checklist, and then dive in to get a better understanding of how Anchor Positioning works.
