- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Sat, 11 Mar 2023 07:46:20 +0000
- To: public-css-archive@w3.org
> > No, this is specifically not the case when serializing custom properties; see https://w3c.github.io/csswg-drafts/css-variables/#serializing-custom-props @cdoublev is right here. Comments are effectively not dropped _within the value_, but the bounds of the value are still determined by tokens, and comments do not produce tokens. Example 17 in Variables is not possible per css-syntax. `--x: /* comment */ 1` becomes `<whitespace-token> <whitespace-token> <number-token>`, then the whitespace tokens are stripped ([consume a declaration](https://drafts.csswg.org/css-syntax/#consume-a-declaration)), which leaves `<number-token>`, and the corresponding original string is then set from that. > Ok, so this is a browser issue. Fully acknowledged, but it's _also_ a spec issue. :-) -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8533#issuecomment-1464853580 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 11 March 2023 07:46:22 UTC