Re: [csswg-drafts] [css-syntax-3] Should a declaration value be consumed as a `<declaration-value>`? (#11315)

In hindsight, to summarize and correct my confusions expressed through my previous comments...

  > In consume a declaration, it is currently consumed as a (unrestricted) list of component values.

No, `<bad-*-token>` and orphan closing tokens are consumed with the declaration value. So nothing to clarify here, this is normal behavior.

  > `color: var(--custom) ];` must be valid at parse time, **if not specified otherwise**.

No, the declaration value is invalid when it includes these tokens, **even nested in a block or function, even if it also includes an arbitrary substitution value**, but except when defined with a forgiving grammar.

I cannot objectively say whether these confusions are worth adding a note after step 5 (consuming the declaration value). So I am leaving this issue open but my questions have been answered.

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


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

Received on Monday, 18 August 2025 13:29:39 UTC