- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Aug 2024 20:32:22 +0000
- To: public-css-archive@w3.org
Unregistered custom properties do not grammar-check at all besides the basic validity of substitution functions in their value. They shouldn't do anything special for `first-valid()` either; that's just part of every property's grammar, and thus included in the "no parsing beyond tokenization" aspect. Remember that one of the reasons we don't grammar-check custom properties is because they can be used to pass around information for non-CSS purposes; we do only the absolute bare minimum of checking (CSS-wide keywords, and other substitution functions) so people can avoid having to think abuot it as much as possible. That said, I think it's reasonable to clarify this in the spec. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10340#issuecomment-2266110149 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 August 2024 20:32:23 UTC