- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Sep 2024 23:21:04 +0000
- To: public-css-archive@w3.org
> arguably undefined Ooor, arguably _defined_. :-) "If a property contains one or more [arbitrary substitution functions](https://drafts.csswg.org/css-variables/#arbitrary-substitution-function), **and those functions are syntactically valid**, the entire property’s grammar must be assumed to be valid at parse time." https://drafts.csswg.org/css-variables/#arbitrary-substitution The examples are not valid because they don't match the grammar of `var()`. This appears entirely intentional and sensible to me. I like how it works now, but I definitely see the problem with `var()` working differently in substitution functions and non-substitution functions. But, ugh, it _would_ be very annoying if we can't select the substitution value (AKA evaluate the function) without first substituting the function contents. It's _even more_ mucking about with tokens before getting to the actual point. -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10947#issuecomment-2375437395 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 September 2024 23:21:05 UTC