- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Thu, 13 Nov 2025 04:38:26 +0000
- To: public-css-archive@w3.org
Wait, hmmmm. Is there really a reason to try and associate some columns as "the same"? Two identical intrinsic tracks in Grid *will* end up different sizes if the items in them contribute differently, so I'm not sure why we want to get a different behavior here. What we want is to just make sure that all the possible positions a spanner can take will fit without overflow, if possible. If we do the "repeat enough times" thing, then we'll get that - in the `repeat(100px auto auto)` with span-2 items example, we'll use 2 repeats, and both `auto`s will end up seeing a 300px span-2 item crossing either a `100px auto` or `auto 100px` track pair, giving both `auto`s a `200px` size. The fact that the `auto auto` pair gives `150px` to each is irrelevant, since they both get `200px` from the other position, and we take the largest. So I think there's no bullet to bite. We just need to: 1. Repeat the repeat() list "enough times", as I outlined above. 2. Generate a hypothetical item per span, and treat it as occupying every possible position. 3. Consider tracks "the same" if they're literally the same track from the repeat() list, across the repetitions. And then reasonable behavior just falls out. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12899#issuecomment-3525316083 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 November 2025 04:38:27 UTC