- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Aug 2021 15:32:51 +0000
- To: public-css-archive@w3.org
andruud has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-variables] Substituting CSS-wide keywords from custom properties themselves == From [substitute a var()](https://drafts.csswg.org/css-variables/#substitute-a-var), Example 13: > While a var() function can’t get a CSS-wide keyword from the custom property itself—if you tried to specify that, like --foo: initial;, it would just trigger explicit defaulting for the custom property—it can have a CSS-wide keyword in its fallback: [etc] But what about this case where the cascade won't intercept the value: ``` @property --x { syntax: "*"; inherits: false; initial-value: unset; } div { color: var(--x); } /* Contains `unset` after substitution, right? */ ``` Should we explicitly specify that CSS-wide keywords are not "computationally independent"? Or do we actually want this behavior? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6502 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 9 August 2021 15:32:54 UTC