- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jul 2024 19:09:20 +0000
- To: public-css-archive@w3.org
I've been looking at making `calc-size()` and `interpolate-size` work for `grid-template-rows` and `grid-template-columns` (in the places where they accept sizing keywords). One thing I've been looking at is the grid layout algorithm: in particular, whether track sizes are considered in the [Initialize Track Sizes](https://drafts.csswg.org/css-grid-2/#algo-init) step or whether they're considered in the [Resolve Intrinsic Track Sizes](https://drafts.csswg.org/css-grid-2/#algo-content) step (in particular, the [Size tracks to fit non-spanning items](https://drafts.csswg.org/css-grid-2/#algo-single-span-items) and [Increase sizes to accommodate spanning items crossing content-sized tracks](https://drafts.csswg.org/css-grid-2/#algo-spanning-items) substeps). My current understanding of the algorithm is (when adding support for these new things) the base sizes set up in the "Initialize Track Sizes" step don't really matter, and there's no need to adjust what happens in *which* step beyond being clear that `calc-size(min-content, ...)` is handled in the same place as `min-content`. I think the only thing that needs to be adjusted is that the full expression needs to be handled in the substeps of the "Resolve Intrinsic Track Sizes" step. But I don't think anything needs to be moved around. I'd appreciate if someone who knows grid could double-check this, though. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-2246075970 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 July 2024 19:09:20 UTC