- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Mar 2022 00:01:12 +0000
- To: public-css-archive@w3.org
Given that we resolve `em`s and the like, I don't see how var() is problematic - they resolve at the same time. (Technically, var()s are even earlier than ems.) Agree that disallowing the CSS-wide keywords syntactically is fine, with them specified to resolve to false if they show up anyway (such as via a variable). fantasai and I think the reasonable options here are: * disallow all css-wide keywords * disallow all except 'initial', allows 'initial' for author convenience since it's just an alias for some other existing property-specific value * disallow all except 'initial' and 'inherit', because these can compute without re-cascading, and asking "is the property the same computed value as its parent" might be useful -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7080#issuecomment-1054829285 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 March 2022 00:01:13 UTC