Re: [csswg-drafts] [css-variables] Custom properties should *not* serialize "exactly as specified" (#7329)

Yeah, we should close open constructs, since the parser doesn't see that the construct isn't properly ended in that case anyway.

The problem is that we do need to exactly preserve things like long strings of digits.

> and what actually happens when things are substituted isn't clear either.

That actually is clear if you're following the spec - the substitution is done with tokens, not characters, and in this example the `--a` property contains a single `<function-token>`, so it'll substitute that. When you later serialize the substituted result you should get `a()`, since you can't tell whether or not the ending token was supplied to a function token.

(To what extent browsers exactly follow the spec here is, uh, up for discussion.)

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


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

Received on Friday, 17 June 2022 23:48:30 UTC