- From: Michaël Vanderheyden via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Nov 2024 15:02:40 +0000
- To: public-css-archive@w3.org
I initially preferred having masonry separated from grid. The main reason was that a lot of developers still struggle with `grid` and the idea of having masonry split from it would allow those developers to have an easier path learning masonry without necessarily having to deal with grid first. However, after reading @jensimmons' [post](https://webkit.org/blog/16026/css-masonry-syntax/), I must acknowledge that `display: masonry` would also mean introducing a bunch of new masonry dedicated properties instead of reusing existing one from grid. IMO, having separate properties would heavily increase the cognitive load for both new and experienced developers. The only way, `display: masonry` would remain a good option is if we were able to reuse all the properties, we need from grid without introducing separate ones, same as e.g. `grid-gap` and `flex-gap` were rid of the prefix to become just `gap`. -- GitHub Notification of comment by Th3S4mur41 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11060#issuecomment-2459992771 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 November 2024 15:02:41 UTC