Re: [csswg-drafts] [css-flexbox-1][css-sizing-3] Definiteness of `min-height: min-content` (#6457)

The CSS Working Group just discussed `[css-flexbox-1][css-sizing-3] Definiteness of min-height: min-content`, and agreed to the following:

* `RESOLVED: min-height:auto just has special behavior that allows child %s to still resolve, and it's not a precedent to apply to all the other content-based keywords. (Thus, we'll remove, or possibly keep-but-reverse, the note that's currently in the spec.)`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic:  [css-flexbox-1][css-sizing-3] Definiteness of min-height: min-content<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/6457<br>
&lt;dael> TabAtkins: We resolved a few weeks ago...the discussion on the call was roughly that min-height:auto needs it special behavior but probably didn't want to extend to other content-sizing keywords<br>
&lt;dael> TabAtkins: Further discussion on issue went back and forth on minor details. Overall everyone agrees that's fine<br>
&lt;fantasai> proposal is https://github.com/w3c/csswg-drafts/issues/6457#issuecomment-917223624<br>
&lt;fantasai> "min-height:auto just has special behavior that allows child %s to still resolve, and it's not a precedent to apply to all the other content-based keywords. "<br>
&lt;dael> TabAtkins: Prop: Accept results of last discussion - all intrinsic sizing keywords besides auto make sizes indefinite for boxes<br>
&lt;dael> Rossen_: Everything but auto makes it indefinite?<br>
&lt;TabAtkins> So, Agenda+ to resolve that min-height:auto just has special behavior that allows child %s to still resolve, and it's not a precedent to apply to all the other content-based keywords. (Thus, we'll remove, or possibly keep-but-reverse, the note that's currently in the spec.)<br>
&lt;dael> TabAtkins: Yeah<br>
&lt;dael> TabAtkins: prop from issue ^<br>
&lt;fantasai> rationale is in dholbert's comment https://github.com/w3c/csswg-drafts/issues/6457#issuecomment-915427806<br>
&lt;dael> TabAtkins: content keywords make it indefinite<br>
&lt;Rossen_> q?<br>
&lt;dael> Rossen_: Reasonable. Any comments?<br>
&lt;fantasai> +1 from me (and dholbert obviously ;)<br>
&lt;dael> Rossen_: Obj?<br>
&lt;dholbert> +1 :D<br>
&lt;dael> RESOLVED: min-height:auto just has special behavior that allows child %s to still resolve, and it's not a precedent to apply to all the other content-based keywords. (Thus, we'll remove, or possibly keep-but-reverse, the note that's currently in the spec.)<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6457#issuecomment-937330433 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 6 October 2021 23:50:38 UTC