- From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Apr 2024 17:39:59 +0000
- To: public-css-archive@w3.org
Commenting here as this is where the community conversation has been directed to, but I still have concerns with the idea of bundling Masonry in with grid. We'll have to account for masonry things in any future additions to grid, and there will be parts of grid that don't make sense in masonry and therefore need explaining as to why they don't work. Given that things like gaps and alignment are already dealt with in other specifications, and there's no reason not to re-use the various methods of sizing columns from grid, having a `display: masonry` (or `display: waterfall` or whatever) makes a lot of sense. Then masonry can be specified with just the things developers need, not having to include things they don't because that's how grid behaves. There's an alternate proposal in https://github.com/w3c/csswg-drafts/issues/9041. I'd also love to see Masonry (via any version of the spec) landed alongside `reading-order-items`. There's a strong possibility of disconnected source vs reading order when using masonry type layouts. There is discussion in https://github.com/w3c/csswg-drafts/issues/5675 about the problems, specifically related to masonry layouts. I think the `reading-order-items` proposal currently being specced [here](https://drafts.csswg.org/css-display-4/#reading-order-items) provides a route to a solution, and it would be great to be able to provide that alongside masonry. -- GitHub Notification of comment by rachelandrew Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9733#issuecomment-2070382976 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 April 2024 17:40:00 UTC