- From: Ryan Leichty via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Apr 2024 14:55:34 +0000
- To: public-css-archive@w3.org
> Should “masonry” be part of CSS Grid? Yes! > Do you want the capabilities to define a single-axis grid with CSS Grid — to use subgrid, spanning, explicit placement, and combining different track sizes? Yes! I also want the ability to use `gap`. > Will you use this at all? What might you do with it? I've had to implement a masonry-like grid twice in the last year, both times having to research the available options, reading through extensive articles and/or documentation for JavaScript based solutions, but ultimately never landing on a perfect option. The proposed solution solves all of our problems and needs. Adding it as a `display` property would be too limiting. > It’s likely masonry is not the best name for this new value. I think `masonry` makes the most sense given it's usage both in blog posts as well as in the names of JavaScript libraries. It has historical context and weight. _Waterfall_ doesn't convey the same kind of visual imagery as bricks stacked on top of each other. -- GitHub Notification of comment by ryanleichty Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10233#issuecomment-2079556577 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 26 April 2024 14:55:35 UTC