- From: Dmitry Statsenko via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Oct 2024 19:31:00 +0000
- To: public-css-archive@w3.org
Think `display: masonry;` would be clearer and more convenient for developers. Based on what I see, the main argument in favor of `masonry layout in grid` a few months ago was the concern that a lot of functionality would be lost if `display: masonry;` were implemented. Now, there are examples showing that the functionality of a separate specification would not left one specification. At the same time, the option of `masonry layout in grid` has many problems, which have been discussed above. The most important one for me — is that in a `masonry layout in grid` implementation, there would be many properties and values valid only for `grid` or only for `masonry`, and to avoid this kind of behavior would be good. Сan't find Mozilla position on this issue. They created the first version of the `masonry layout in grid` specification and implemented it in an experimental browser version, but what do they think about the advantages and disadvantages of `display: masonry;`? It would be interesting to read their position. -- GitHub Notification of comment by alkorlos Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2394444241 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 October 2024 19:31:01 UTC