- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Dec 2020 01:25:29 +0000
- To: public-css-archive@w3.org
> I think the current spec in 5.2.1.c dictates that specified size suggestion is `0px` in this case. @fantasai said that this compressible behavior was needed for compat, and it looks like it was originally for images in tables -- I doubt replaced elements as flexbox items had compat problems back in 2017. So, my point is, I'm not sure why the flex/grid automatic minimum size stuff was ever put in 5.2.1c. There probably was a good reason, I just don't know it and I'm confused by the results. It looks like that spec text was added to 5.2.1c in https://github.com/w3c/csswg-drafts/commit/534f79283a4687a5f0bc722baed5792e2c54433a, with a bit of explanation in https://github.com/w3c/csswg-drafts/issues/2674#issuecomment-465490328 In particular, the intent of the change was 'to make the cyclic percentage rules that zero out percentages apply to automatic minimum size calculations, making the “specified size suggestion” definite (and equal to zero, in the case of a pure percentage).' It looks like this was briefly discussed in the subsequent CSSWG meeting, as quoted in the next comment there. I think this all means that @davidsgrogan is correct that the specified size suggestion is indeed `0px` in this case, which means Chrome's rendering of the original testcase is correct. It's true that there isn't any cyclic dependency, but that doesn't matter; the spec says we should apply the same rule, and we should resolve the percent to 0, for the purpose of computing the specified size suggestion. -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5665#issuecomment-741393120 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 December 2020 01:25:31 UTC