- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Apr 2024 22:55:46 +0000
- To: public-css-archive@w3.org
We flagged this for the agenda in order to have a discussion of the pros and cons of building masonry into Grid vs creating a new display type. There's a multitude of different considerations, but some of the key ones have been outlined [above](https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-1710838816) and in https://github.com/w3c/csswg-drafts/issues/10233; they include - Whether masonry is philosophically and conceptually a grid or not. - Whether track size variation is needed, and what performance costs it might have vs enforcing a uniform track width. - Whether integrating masonry and grid layout models and intertwining their feature sets is a pro or a con, both wrt usability of CSS for authors and wrt feature development in specs and implementations. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2071086963 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 22:55:47 UTC