- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Nov 2022 00:41:37 +0000
- To: public-css-archive@w3.org
> The first two are the exact use-cases I was afraid we might kill - people storing JSON in custom props. I think this is reasonable to do, and would like to not remove it if possible! But notably, these all have the braces as the very first token in the value, which is theoretically amenable to being recognized. > > The third looks like someone accidentally used a plain string in JS rather than a template string, so it's just an error. > > The fourth is in a CSS string, so not relevant for our purposes - only top-level curlies matter for this question. Given that you cannot have empty pseudo-classes, these would still be parsed as declarations, right? It's braces in the middle of a value that we could not have (sure, this would still preclude some JSON values, but not those). -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7961#issuecomment-1314599911 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 November 2022 00:41:40 UTC