Frequently Asked Questions [CSS Working Group Wiki]
Rebuttals to the most oft-asked requests for browsers to change the way they handle CSS.
Let’s Define CSS 4 · Issue #4770 · w3c/csswg-drafts
Jen kicked off a fascinating thread here:
It’s come up quite a few times recently that the world of people who make websites would greatly benefit from the CSS Working Group officially defining ”CSS 4”, and later “CSS 5“, etc.
The level is discourse is impressively smart and civil.
Personally, I don’t (yet) have an opinion on this either way, but I’ll be watching it unfold with keen interest.
Related links
699: Jeremy Keith on Web Day Out – ShopTalk
This episode of the Shop Talk Show is the dictionary definition of “rambling” but I had a lot of fun rambling with Chris and Dave!
Help us choose the final syntax for Masonry in CSS | WebKit
I really like the way that the thinking here is tied back to Bert Bos’s original design principles for CSS.
This is a deep dive into the future of CSS layout—make a cup of tea and settle in for some good nerdiness!
An alternative proposal for CSS masonry | Blog | Chrome for Developers
Rachel responds to Jen’s recent post with the counter-argument; why masonry should be separate from grid.
I’m not entirely convinced. We heard performance issues as a reason why we could never have container queries or :has, but here we are. And the syntax for a separate masonry spec borrows so heavily from grid that it smells of redundancy.
Help us invent CSS Grid Level 3, aka “Masonry” layout | WebKit
This is a wonderful in-depth article by Jen, with lots of great demos.
She makes a very strong case for masonry layouts being part of the grid spec (I’m convinced!). If you have strong feelings one way or the other, get involved
Related posts
Toast
Jeremy is not eating toast.
Progressing the web
Don’t let the name distract you—progressive web apps are for everyone.