- From: Sam Windsor via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Oct 2024 03:17:06 +0000
- To: public-css-archive@w3.org
I also initially favoured Chrome's proposal but after reading WebKit's justification for "Just Use Grid", I agree with their reasoning for `display: grid` as per design principles. 1. Reuse existing patterns and properties 2. It should be simple to learn and simple to use Both of these support Just Use Grid instead of having to learn an entire new syntax and layout system. Further, I see points raised as to how difficult `display: grid` would be if masonry use cases changed or expanded, but this doesn't make sense as we can simply override properties and implement new ones without creating an entire new syntax and properties, the same way we do already with existing layouts and properties. New masonry specific related properties can be added to `display: grid`, or existing properties adapted in line with reusability, _if_ such use cases arise and are required without disrupting how it currently operates at a basic level inline with current use and understanding. In an extreme case, `display: masonry` can still be implemented in future if masonry ever grew to be so unique and adaptable to require its own layout system. -- GitHub Notification of comment by windsywinds Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11060#issuecomment-2440457586 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 October 2024 03:17:07 UTC