- From: Robin Miller via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Sep 2024 20:16:30 +0000
- To: public-css-archive@w3.org
FWIW from a rando dev: After reading [Rachel Andrew](https://rachelandrew.co.uk/archives/2024/09/21/masonry-and-good-defaults/)'s argument, I too am **strongly in favour** of `display: masonry`. IMHO, the [Safari team](https://webkit.org/blog/15269/help-us-invent-masonry-layouts-for-css-grid-level-3/)'s argument that it's _grid with an exception on one axis_ undervalues how confusing exceptions are for learning and comprehension (citation: spelling and grammar in the entirety of the English language). Another small benefit of `display: masonry` is the conceptual rhyming with `inline-block`. When you need some of the behaviour of `inline`, and some of the behaviour of `block`, there's a midpoint available. As several others have pointed out, masonry is a bit like `grid` and a bit like `flex`: Flex: Control 1 dimension, fill 1 dimension Masonry: Control 1 dimension, fill 2 dimensions Grid: Control 2 dimensions, fill 2 dimensions -- GitHub Notification of comment by robinetmiller Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2377853707 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 September 2024 20:16:31 UTC