- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Jun 2024 21:12:38 +0000
- To: public-css-archive@w3.org
These shouldn't be merged, imo. They're doing the same things, conceptually, but have a totally different set of controls for those things. We'd just have two divergent syntax branches, with one useful only for Grid and the other useful only for Masonry; we'd have to define default behavior for if you used the wrong set of keywords. That doesn't suggest they're actually useful to be in the same property. (This is ignoring the larger issue about Masonry being a different display type in the first place; regardless of that, I think they're still best as separate properties. But if it is a separate display type, they're clearly best as separate properties imo.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10231#issuecomment-2189979119 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 June 2024 21:12:39 UTC