"You might even be current on the ongoing debate about how it should be built, with two big proposals on the table, one from the Chrome team and one from the WebKit team. The two competing proposals are interesting in their own right. Chrome posted about its implementation a while back, and WebKit followed it up with a detailed post stating their position (which evolved out of a third proposal from the Technical Architecture Group)."
"We'll rehash some of that in this post, but even more interesting to me is that this entire process is an excellent illustration of how the CSS Working Group (CSSWG), browsers, and developers coalesce around standards for CSS features. There are tons of considerations that go into a feature, like technical implementations and backwards compatibility. But it can be a bit political, too."
Two major proposals for CSS Masonry have emerged: a Chrome approach using display: masonry as a distinct layout model, and a WebKit approach evolved from a TAG proposal. Masonry stacks unevenly sized items along a single track that wraps into multiple rows or columns, unlike Grid or Flexbox. The feature involves trade-offs including technical implementation, default behavior alignment, and backwards compatibility. Early prototypes appeared in Firefox in 2019 by integrating masonry into Grid. Chrome later argued masonry merits its own display value because Grid defaults do not align with masonry behavior. Standardization involves CSS Working Group decisions, browser influence, and developer feedback.
Read at CSS-Tricks
Unable to calculate read time
Collection
[
|
...
]