[csswg-drafts] [css-sizing] clarification around Compressible Replaced Elements and min-content size (#5665)

davidsgrogan has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-sizing] clarification around Compressible Replaced Elements and min-content size ==
[5.2.2 Compressible Replaced Elements](https://drafts.csswg.org/css-sizing/#min-content-zero) applies to 5.2 _Intrinsic Contributions_. Does it also apply to 5.1 _Intrinsic Sizes_?

The answer affects the size of the `<input>` below.

<div style="display: flex; width: 150px;">
  <div style="flex: 0 0 100px;"></div>
  <input style="width: 100%">

Indications that 5.2.2 applies to 5.1:
 * The text of 5.2.2 explicitly says min-content size, which is clearly in the purview of 5.1: `The following elements can have their min-content size compressed`

Indications 5.2.2 does not apply to 5.1:
 * 5.2.2 is only in the 5.2 section, not an independent section like a hypothetical 5.3
 * 5.2.2 refers to 5.2.1 for clarification about when min-content sizes can be "compressed"

Chrome behaves as if 5.2.2 applies to 5.1. Firefox behaves as if it does not apply. (In an unlikely scenario, the implementors of the respective engines think the other engine is right.)

Can we get this part of the spec clarified so we know how to size the `<input>` element in the above example? One [suggestion](https://bugs.chromium.org/p/chromium/issues/detail?id=581545#c15) from the [chrome bug](https://crbug.com/581545) is
1. Replace "compressible" with a clearer term
2. Make sure the two places match about whether this affects min-content size or contribution

The firefox bug is at https://bugzilla.mozilla.org/show_bug.cgi?id=1585485

/cc @dholbert @cbiesinger who I've been discussing this with

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5665 using your GitHub account

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

Received on Monday, 26 October 2020 22:40:06 UTC