- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Sep 2021 21:54:34 +0000
- To: public-css-archive@w3.org
As Oriol mentioned, min-content and max-content differ in the block axis when sizing flex and grid containers, because min-content sizing doesn't distribute any free space. The original question still remains: the spec is currently implying that the content-based sizing keywords in the `min-*` properties don't prevent children from resolving %s against those sizes (even though the `width/height` properties themselves do). This is *necessary* behavior for the automatic minimum size (or else percentages would *usually* be unresolvable), which can be content-based, so it *seems* like it should be fine to specify that explicitly for all the content-based sizing keywords. But given that these keywords aren't otherwise representing definite sizes, do we actually want to? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6457#issuecomment-914653447 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 September 2021 21:54:36 UTC