There's been a lot of discussion about masonry in CSS recently. I wrote about the Chrome team's proposal to help clarify why we have concerns with bundling masonry in with grid, and to show that a separate spec doesn't mean fewer features. https://developer.chrome.com/blog/masonry #css
An alternative proposal for CSS masonry  |  Blog  |  Chrome for Developers

A proposal to define masonry and grid in different specifications.

Chrome for Developers
@rachelandrew this makes a lot of sense, reading it. Cheers for the explainer; I didn't know half this stuff!
@rachelandrew Thanks for putting this together. You articulated the concepts so clearly. ❤️

@rachelandrew @tomayac should masonry not be considered a 2D flex layout?

Looking at one of the example of your blog, wouldn’t it be great if we could add some grow: auto on these placed or spanned blocks to fill the gaps?

Also what would be nice if we could consider the first two columns one block and it would all be two columned text and the ‘overlapping’ block would instead of overlap push the content away as if there is a floating item in that text box.

@rachelandrew Yes! Great post!

I'm still not convinced masonry should have an official CSS specification, but at least it doesn't need to pollute the grid spec.

@rachelandrew I am not sure if the following critique is reaching the wrong person with you so excuse me if not. But the automatic translation to German of this post I got is such utter shit it would be way better to just have it in English only.
@rachelandrew Mostly because of the fact that all technical terms are translated in a literal and very cringe way. But also the rest of the language sounds very strange, somehow robotic and very unnatural.
@kraftner I'd suggest you switch to the English version then. Unfortunately we can't translate by hand all of our content into every language, so machine translation means that people who can't read the English version have something. Is it perfect? No. Is it better than nothing? We have data that shows it's appreciated by many people.
@rachelandrew Obviously I did that. Also sorry if my message was too harsh. In reading it again I could have phrased that better and more constructive: Maybe there is some way to at least mark some technical words like Masonry or Grid as untranslatable terms which would already greatly improve the output if that is possible technically.
@rachelandrew @kraftner I learned the term masonry only in the context of UI-lay-outs. To me it just meant Pinterest (layout), so without the translation (which also slightly irritated the me who prefers the original esp. for tech docs and thinking his understanding of English is in general sufficient) I wouldn’t have been made aware of its original meaning, related to brick-based construction 😅