The CSS Masonry layout feature is evolving through competing proposals from Chrome (display: masonry) and WebKit (grid-based with item-flow). This debate illustrates how CSS features develop through the CSS Working Group's consensus process, where browsers prototype implementations, gather developer feedback, and negotiate technical trade-offs. The article examines lessons from Flexbox and Grid's evolution, explaining how browser politics, technical merit, and developer input shape web standards. Currently, the CSSWG has resolved that masonry will be a new display type including 'grid' in its name, while adopting the item-flow approach for implementation.

10m read timeFrom css-tricks.com
Post cover image
Table of contents
Masonry RecapHow CSS Features EvolveThe CSSWG’s RoleThe Bigger PictureWhere We’re AtFurther reading
1 Comment

Sort: