- From: Angel Ponce via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Sep 2024 16:58:17 +0000
- To: public-css-archive@w3.org
I'd like to add my support for integrating masonry layout into CSS Grid rather than creating a separate `display: masonry`. Combining masonry with Grid could unlock the full potential of Grid's features like subgrid, track sizing, item placement and others. This integration allows for more complex and dynamic layouts that we might not be able to achieve with a standalone Masonry display. I think the arguments for a separate `display: masonry` focus too much on the potential simplicity at the expense of functionality. Excluding Grid's powerful features would hinder developers who want or need more than basic layouts. Plus, introducing another display type could lead to confusion and fragmentation in the layout ecosystem. Some argue that masonry is fundamentally different from Grid because it aligns items in one dimension, but I strongly believe Grid is flexible enough to handle both one-dimensional and two-dimensional layouts. Separating masonry from Grid overlooks this versitality. TL;DR, integrating masonry into CSS Grid provides greater flexibility and promotes a more cohesive approach to layout design. It makes more sense to enhance the tools we have rather than fragmenting them, IMHO. -- GitHub Notification of comment by angelux Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2364142759 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 September 2024 16:58:18 UTC