- From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
- Date: Sun, 22 Sep 2024 21:47:41 +0000
- To: public-css-archive@w3.org
> If those who support `display: masonry;` believe there are specific reasons or properties that justify the independent evolution of Masonry, I’d be keen to hear them. In addition to [the post on the Chrome blog](https://developer.chrome.com/blog/masonry-syntax) that outlines a number of places where masonry in grid has the potential to be confusing, I've outlined (as someone who has been teaching CSS for about 25 years) _why_ it's confusing, and not particularly ergonomic, due to the fact the best defaults are different—[Masonry and good defaults](https://rachelandrew.co.uk/archives/2024/09/21/masonry-and-good-defaults/). Reusing existing properties is more confusing, not less, if those properties behave in different ways. As for there not being complaints from developers about the existing implementations, those implementations are experimental, so very very few people will have done any more than a quick demo, and those people are likely to be very experienced with CSS (as those are the folks who like to play around with experimental CSS). So that's just not a great signal, and is why making these decisions is hard, and why people who have experience teaching the language can help, as we do get a read on what people find hard. -- GitHub Notification of comment by rachelandrew Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2366980228 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 22 September 2024 21:47:42 UTC