- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Jun 2021 17:22:50 +0000
- To: public-css-archive@w3.org
> That would mean a behavior change, in practice, for all the layout modes though, as demonstrated by Oriol's second testcase. I think we've strayed away from that original "just rerun layout using this value instead" conception pretty thoroughly. This isn't quite whats going on here - it wouldn't involve a change for all layout modes, just a clarification for what should happen with grid. Firefox's behaviour is a little more self consistent just viewing grid layout by itself. Effectively Firefox is applying the "grid rule" that once the "used block-size" is found, we re-compute the grid using that new "used" size in order to re-resolve percents, frs, %-grid-gaps, etc. Normally we don't consider 'auto' tracks when re-computing the grid, as it (typically) doesn't change the result. However flex-items are special in that they can "force" the initial block-size to be indefinite, even though You can trigger "inconsistency" in Blink's behaviour by added a %-gap or similar to the above testcase. E.g. with a %-gap we behave like Gecko due to recomputing the grid using the "used" block-size. I think I'd be happy to align on Firefox's behaviour here. -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4852#issuecomment-870779107 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 June 2021 17:22:52 UTC