- From: Carlos Araya via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 May 2024 21:33:59 +0000
- To: public-css-archive@w3.org
> +1 to team Safarifox on this one. > > The masonry layout solution should be part of Grid, not its own display. As someone pointed out in another comment, it is sometimes hard distinguishing Flex from Grid, and being able to use features of Grid with a masonry layout feels very nice. Honestly, the masonry layout kinda feels like being able to marry Flex and Grid in a very natural way. How much complicated would this make the grid specification? You will have to learn all the ways where masonry and grid are different in addition to what they have in common. I don 't believe this will be trivial. Having a separate `display: masonry` value means that you keep grid as is and can learn masonry as something different and specific. -- GitHub Notification of comment by caraya Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10233#issuecomment-2096962187 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 May 2024 21:34:00 UTC