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

cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-values-5] Should `<whole-value>` functions be parsed before the declaration value range? ==
CSS-wide keyword parsing should kick in first because `--custom: initial` should result to `--custom` being declared to its initial (guaranteed-invalid) value rather than the `<ident-token>` for `initial` (the result from matching against its value definition).

Arbitrary substitution parsing should then kick in before the value range because `--custom: var(1)` should be invalid. They should be parsed before `<whole-value>` because `display: var(--empty) first-valid(block)` should be valid (at parse time, at least).

Should `--custom: first-valid(not, whole) value` be valid?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10340 using your GitHub account


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

Received on Thursday, 16 May 2024 04:25:07 UTC