W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2018

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

From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
Date: Wed, 31 Jan 2018 19:08:17 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-293276169-1517425696-sysbot+gh@w3.org>
dholbert has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-sizing] Decide how to handle `min-width/min-height: auto` for non-grid/flex items ==
In #2230, the CSSWG resolved to make `min-width/min-height: auto` always compute to itself (though per https://github.com/w3c/csswg-drafts/issues/2230#issuecomment-362015241 , this was only with regards to flex and grid items).

What should happen for other elements?  Right now the spec doesn't say (so it implies that it'd still compute to itself everywhere, which I don't think matches reality)...  Previously [it was defined as computing to 0](https://www.w3.org/TR/2016/CR-css-flexbox-1-20160526/#min-size-auto) for these elements.

Suggestion: how about we say the [resolved value](https://drafts.csswg.org/cssom/#resolved-values) of this `auto` keyword should be 0 for any non-grid/flex item.  (This is basically what we've got implemented in Firefox, for non-grid/flex items -- i.e. we store `auto` internally in the computed style, and then we check the styles.)  I'm guessing that might be what other engines do, too, though I don't know for sure (CC @Rossen @cbiesinger)

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2248 using your GitHub account
Received on Wednesday, 31 January 2018 19:08:50 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:23 UTC