Open Bug 1672559 Opened 4 years ago Updated 2 days ago

[css-sizing-3] Honor min-content, max-content, fit-content in the min-height and max-height properties (or more generally min/max block-size properties)

Categories

(Core :: Layout, defect)

defect

Tracking

()

People

(Reporter: mozilla-apprentice, Unassigned)

References

Details

A resolution was made for csswg-drafts/#3973.

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

  • RESOLVED: accept edits made

Discussion.

To clarify a bit, the edits here (which we need to implement) are to honor min-content etc. in the min-block-size and max-block-size properties (e.g. min-height and max-height, under the default writing mode).

Previously those keywords were defined as equivalent to auto, in the block axis in general. Now, I think they're only equivalent to auto for block-size (i.e. height), but not for other properties.

One implication of this change: on a flex item, min-height:min-content and min-height:max-content should just refer to the content size, and should not trigger the automatic minimum size computation (which has several other non-content-related considerations).

Summary: [css-sizing-3] Why was min-content, etc. redefined to do nothing in the block axis? → [css-sizing-3] Honor min-content, max-content, fit-content in the min-height and max-height properties (or more generally min/max block-size properties)

Note per https://github.com/w3c/csswg-drafts/issues/6457 : once we honor these keywords as triggering content-based sizes (in {min/max}-{height/width}, we'll need to make sure they force the box's final size to be considered indefinite, per CSSWG resolution in https://github.com/w3c/csswg-drafts/issues/6457#issuecomment-937330433

(at least for the block axis)

You need to log in before you can comment on or make changes to this bug.