- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Sep 2023 23:21:17 +0000
- To: public-css-archive@w3.org
What I mean is, since there is *no* column auto-selection *at all*, this isn't Masonry. Masonry's entire reason for existing is to allow you to place items according to the tracks' current fill height; if you're skipping that entirely, then Masonry might not be the right abstraction for this. This is especially true if reusing Masonry as the layout abstraction for this (and making changes to accommodate it) would harm more core use-cases. On the other hand, nothing about this case is particularly unusual for Grid. New functionality is needed (flowing multiple items into one cell as if they were grouped into a container element), but it's immediately compatible with the rest of Grid, too; it doesn't force us to reshape anything *else* about grid to accommodate it. As far as Grid is concerned it's *exactly* like just having a container element filled with stuff, and that's exactly what the use-case needs and wants out of it. So yes, in theory we could address *some* variations of this "flow multiple items into one grid cell" use-case with Masonry, but we can't hit all of them, and even for the ones we can do, it requires adding additional features to Masonry that harm the core use-cases. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-1710879653 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 September 2023 23:21:20 UTC