Re: [csswg-drafts] [css-sizing] Decide how to handle `min-width/min-height: auto` for non-grid/flex items

The Working Group just discussed ``[css-sizing] Decide how to handle `min-width/min-height: auto` for non-grid/flex items``, and agreed to the following resolutions:

* `RESOLVED: Accept the change in https://github.com/w3c/csswg-drafts/issues/2248#issuecomment-362114572`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-sizing] Decide how to handle `min-width/min-height: auto` for non-grid/flex items<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2248<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/2248#issuecomment-362114572<br>
&lt;dael> fantasai: The issue is about what do we do with computed values on non-grid and non-flex items. Behave as 0. dholbert proposed auto keyword computes to itself on all display types, but the resolved value should be 0.<br>
&lt;dael> fantasai: This has a couple of advantages. One is that it makes the computed value easier to compute, the keyword isn't based on display type information. Second advantage is there was some behavior we were trying to resolve for anotehr issue which required us to distinguish between auto and 0 min sizes on elemnts that are no flex and grid so being able to refer to that is good.<br>
&lt;dholbert> *resolved &amp; used (i guess)<br>
&lt;dael> fantasai: Disadvantage if you're animating from initial value of assumed 0 on the min-height and min-width, that breaks.<br>
&lt;dael> fantasai: No sure how many people are animating that and, if they are, assuming initial value of 0.<br>
&lt;dael> fantasai: I think we should take proposal, but want to hear from group. Toward the end of the issue there's discussion about a separate item that needs to file separately.<br>
&lt;dael> astearns: Other opinions?<br>
&lt;dael> astearns: Proposal is have the computed value be auto but the used value be 0?<br>
&lt;dael> fantasai: Used value is 0. Resolved value would be 0. CHange...currently computed value is 0, computed value remains as the keyword auto. If you use getComputedStyle we'll return 0 for backwards compat<br>
&lt;dael> fantasai: Kinda like we do for width where auto computes to self but getComputedStyle returns 0<br>
&lt;dael> astearns: Objections to this change?<br>
&lt;dael> RESOLVED: Accept the change in https://github.com/w3c/csswg-drafts/issues/2248#issuecomment-362114572<br>
</details>


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

Received on Wednesday, 14 February 2018 17:46:21 UTC