- From: fantasai via GitHub <noreply@w3.org>
- Date: Mon, 11 Aug 2025 16:45:03 +0000
- To: public-css-archive@w3.org
Jen and I did a deep dive into the auto-sizing behavior that we'd get from `repeat(auto-fill, auto)` here: https://webkit.org/blog/16026/css-masonry-syntax/#extending-masonry-with-repeatauto-fill-auto Our conclusion was that while it's useful in some cases (like a footer sized to the max-width of the longest menu item label), it doesn't actually do anything particularly useful by default. For typical masonry layouts (cards, photos) you have to put some not-obvious sizing controls on the items themselves, at which point it's better for the author to be putting that info into their track sizing declaration directly: they have access to more power that way, and it's more performant for the browser to not have to analyze all the items. For these reasons, we think it's better to nudge authors into using track sizing rather than leading down the path of trying to influence track sizing by sizing the items, which is what having this kind of automatic default would do. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10869#issuecomment-3175851349 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 August 2025 16:45:04 UTC