Re: [csswg-drafts] [css-values-5] Should `<whole-value>` functions be parsed before the declaration value range? (#10340)

  > Unregistered custom properties just tokenize, except for a few things like `var()` and `env()`.

I did not considered this option. So `--custom: first-valid(not, whole) value` is valid but not `--custom: first-valid(1) var(--empty, var(invalid))`, and a CSS parser should therefore not try matching `<whole-value>` as a replacement for a custom property value, but only for standard properties?

Even if `first-valid(not, whole) value` is guaranteed to be valid in any declaration value, it would probably not be usefull to make it invalid at parse time also for a custom property value. It just seems more consistent though.

-- 
GitHub Notification of comment by cdoublev
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10340#issuecomment-2123323424 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 21 May 2024 19:43:31 UTC