- From: Andrei Sirotin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Sep 2024 16:00:11 +0000
- To: public-css-archive@w3.org
overall, I support grid masonry as it adheres to familiar API and I don't have to remember that much extra stuff. Now, if display: masonry would have it's own "unique" syntax and would have no resemblance to grid, then it's fine to keep them separate. But, if they start sharing syntaxes then I'm afraid it will cause more confusion as developers would have to remember which syntax applied to which display and how it behaves + the defaults would also be different. On the complaints that the grid is already complex enough, as @cat394 said, I'm also interested in what **specifically** is complex about it that masonry would increase. as I understood from chrome blog post, they have achieved similar performance on both approaches so the only discussion is about the syntax of it. -- GitHub Notification of comment by andrei9669 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2374496770 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 September 2024 16:00:12 UTC