- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Jun 2019 04:53:21 +0000
- To: public-css-archive@w3.org
>I think key word is "will", meaning that some other spec text will say how/when that's applied. That's right, see https://github.com/w3c/csswg-drafts/issues/3567. The min and max cannot always be compared a priory, so each time we handle max<min needs to be explicitly defined. I agree the proposal makes sense, i.e. - If both the min and max track sizing functions are definite, use the maximum of them - If only one track sizing function is definite, use that one And I think there is the remaining case of both sizing functions being indefinite, like a grid container with `width: max-content; max-width: 100px; grid-template-columns: repeat(auto-fill, 50%)`. This falls into this case because the max size is definite, but the preferred size is intrinsic, so the percentage track size is initially treated as `auto`, right? -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4043#issuecomment-503862471 using your GitHub account
Received on Thursday, 20 June 2019 04:53:22 UTC