- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Apr 2023 12:11:51 +0000
- To: public-css-archive@w3.org
cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-variables] Invalid arbitrary substitution values as `<declaration-value>` == Is it ok that Chrome/FF do not accept `var(--custom, var(--))` at parse time? I would have rather said it is invalid at computed value time. > `var() = var( <custom-property-name> , <declaration-value>? )` https://w3c.github.io/csswg-drafts/css-variables-2/#using-variables > The `<declaration-value>` production matches any sequence of one or more tokens, so long as the sequence does not contain `<bad-string-token>`, `<bad-url-token>`, unmatched `<)-token>`, `<]-token>`, or `<}-token>`, or top-level `<semicolon-token>` tokens or `<delim-token>` tokens with a value of "!". It represents the entirety of what a valid declaration can have as its value. https://w3c.github.io/csswg-drafts/css-syntax-3/#any-value I guess they are recursively looking all `var()` in the input list of component values and validate their arguments. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8771 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 April 2023 12:11:53 UTC