Re: [csswg-drafts] [css-grid-3] intrinsic track sizing algorithm for masonry can go exponential in complexity. (#10053)

I really think that spanning items should _not_ contribute to the width of the columns in masonry. Even in a regular grid, this is the behavior that I find unnecessary and often harmful, and I don't think there are many legit use cases for wanting this in a masonry layout. As an author, when I want some element to span other columns/rows, I want it to _adapt_ to whatever there is, not to _contribute_. (copying this part from https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2074586448)

When some `auto` column has _only_ spanning items contributing to it, I would rather consider it be `minmax(0px, 1fr)` (when with regular `auto`) or just `0px` when it is in a repeating context.

-- 
GitHub Notification of comment by kizu
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10053#issuecomment-2074596596 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 24 April 2024 10:11:09 UTC