- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Sep 2021 17:24:16 +0000
- To: public-css-archive@w3.org
If I'm not misunderstanding anything in my previous comment here, then I think I'd prefer that we have these min-content/max-content keywords consistently prevent sizes from being definite. I think we can consider `min-height:auto` to be special, given that: (a) it's the default, and we don't want percentages to just be broken by default. (b) it doesn't require content measurement in every layout mode (e.g. for a child of a block) (c) even in layout modes where it does perform content measurement, it has special-cases where it still doesn't need to (e.g. `overflow:scroll` flex items will resolve `min-main-size:auto` to `0`). In contrast: (d) `min-height:min-content` is not the default, so if we say it makes its element indefinite-height, that's not going to break percentages across the board. (Just for that one element.) (e) `min-height:min-content` is (I think) intended to always trigger content measurement, in all layout modes. It's not as subtle "sometimes-yes-sometimes-no" like `auto`. Given the above, I'd lean towards speccing the content keywords as triggering indefinite sizes (or at least, I'd lean against speccing the opposite). -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6457#issuecomment-915427806 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 September 2021 17:24:17 UTC