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!
Overflowing content, browser support, and polyfill updates
byJames Stuckey Weberon
Anchor positioning is close to Baseline. As more people try it out, they are finding areas where it could be improved, and differences between browsers. Let’s take a look at the current state of anchor positioning.
We don’t have to choose between px and rem for spacing
byMiriam Suzanneon
There are many articles and established CSS best-practices that rely on determining the correct or best units to use. Now that comparison functions are well supported in CSS, we don’t have to choose.
It’s time to stop spreading this out-dated practice
byMiriam Suzanneon
Setting the box-sizing model to border-box is one of the few remaining CSS ‘resets’ used across most projects. But there are two common approaches, and the more popular choice will cause more problems than it solves.
