Ahmad ShadeedMasonry should be part of grid.
Making it `display: masonry` doesn't work in real-life use-cases (complex CSS, responsive variations, etc).
+ a new display value feels like duplicating the grid syntax but with a new name. Doesn't feel right.
I'm getting back on track but slowly, I might write a few thoughts on that.
The `display: masonry` always reminds me of the `display: bootstrap` April fool I shared a few years ago.
Let's hope it will be part of CSS grid.
alcinnz@shadeed9 Yes, please!
As I've just wrote as I shared this blogpost: Give me that tasty graceful degradation into Grid!
Angel Ponce@shadeed9 I think the WebKit team hit the nail on the head when they said the Chrome team’s argument works better in isolation than in real life. My team and I are working on a big refactor and can clearly see how the Grid approach is more effective in practice than in isolated examples or when focusing solely on pre-emptive optimization.
On a personal note, I feel the Chrome team has been quite forceful in pushing their point of view—after all, we’re all friends on the web!
@angelux I agree! I remember looking at the mentioned article in Chrome’s blog and I wasn't interested because of the purely abstract examples.
I’m trying to wrap my head around the spec and share my thoughts in an upcoming blog post.