- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Sat, 26 Feb 2022 21:44:35 +0000
- To: public-css-archive@w3.org
> Run the grid algorithm again, now with a definite available grid space, and not treating the subgrid as empty. It shouldn't matter if the outer grid (which I think you're referring to here) has a definite size or not. If you re-run the grid algorithm you'll reset any sizes of the columns/rows, (and the subgrid doesn't have a defined size at this point). If you inspect children here you'd break containment afaict. I believe we'll need either option (1) or (2) above as with container queries you can have grandchildren change their grid-template (e.g. a grandchild may go from `grid-template-columns: subgrid` to `grid-template-columns: initial`) or change their grid-area affecting placement, along with a whole host of other things. -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7091#issuecomment-1052661228 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 26 February 2022 21:44:37 UTC