W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2019

[csswg-drafts] [css-sizing-3] Why was min-content, etc. redefined to do nothing in the block axis? (#3973)

From: Christian Biesinger via GitHub <sysbot+gh@w3.org>
Date: Sat, 25 May 2019 01:48:21 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-448400080-1558748900-sysbot+gh@w3.org>
cbiesinger has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-sizing-3] Why was min-content, etc. redefined to do nothing in the block axis? ==

https://drafts.csswg.org/css-sizing-3/#sizing-values

> min-content
> If specified for the inline axis, use the min-content inline size; otherwise behaves as the property’s initial value.

Why is it now defined this way (it didn't use to be)? This makes it impossible to use this property in min/max-block-size properties, which is useful.

(Chrome's UI was using it, until https://chromium-review.googlesource.com/c/chromium/src/+/1599691 broke it when we matched the spec)

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3973 using your GitHub account
Received on Saturday, 25 May 2019 01:48:26 UTC

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