- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 May 2024 23:33:03 +0000
- To: public-css-archive@w3.org
@jgthms but how treating Masonry as 1-dimensional layout could account for items spanning multiple columns, as most examples in the documentation of Masonry by @desandro show? It clearly seems to introduce the horizontal dependencies between columns (you have to check the height of neighbouring columns as well while choosing where to put the next element), and these dependencies can be considered "virtual row lines". And limiting the possible layout to single-column version would exclude "magazine layouts" like [in this example](https://github.com/w3c/csswg-drafts/issues/9733#issuecomment-2097183433). To me, Masonry is still 2-dimensional, and @desandro himself describes his library as a "Cascading _grid_ layout library". I see the key difference from the regular Grid, which works "from layout in" in both direction, that Masonry works from layout in in one direction and from content out (like Flexbox) in another. However, differentiating 2-dimensional "masonry grids" and 1-dimensional "masonry columns" (like "masonry" vs. "waterfall" [in the comment above](https://github.com/w3c/csswg-drafts/issues/10233#issuecomment-2087442341)) might make sense. -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10233#issuecomment-2103603334 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 May 2024 23:33:03 UTC