W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2021

Re: [csswg-drafts] [css-values-4] min/max(%, %) should explicitly evaluate against the % value, not the resolved value (#4227)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Jan 2021 21:45:17 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-768597565-1611783917-sysbot+gh@w3.org>
Yes, Oriol is correct. %s *cannot* (in general) be correctly resolved at computed-value time, so we're sticking with the current spec text that doesn't let them simplify at all (until they're later replaced by a `px` value or whatever)

GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4227#issuecomment-768597565 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 January 2021 21:45:19 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:25 UTC