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

[csswg-drafts] [css-sizing] Computing min-width/min-height: auto to zero

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Sat, 27 Jan 2018 03:21:41 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-292085300-1517023300-sysbot+gh@w3.org>
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-sizing] Computing min-width/min-height: auto to zero ==
When exactly does 'auto' compute to zero?


The  wording in Flexbox https://www.w3.org/TR/css-flexbox-1/#min-size-auto isn't particularly clear.

> On a flex item whose overflow is visible in the main axis, when specified on the flex item’s main-axis min-size property, specifies an automatic minimum size. It otherwise computes to 0 (unless otherwise defined by a future specification). 

Does it compute to zero
- on flex items, in the main axis, when 'overflow' is visible?
- on flex items, in the main axis always, but not in the cross axis? (Firefox does this)
- on flex items, in both axes? (Chrome does this)

We should probably bias towards computing to `auto` in as many cases as is Web-compatible, but we should also fix the spec to say exactly what happens.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2230 using your GitHub account
Received on Saturday, 27 January 2018 03:21:44 UTC

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