- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Sat, 12 Nov 2022 00:05:52 +0000
- To: public-css-archive@w3.org
Yeah, specifically I mean there not parsing a string as a CSS value, instead just letting strings be keyword values. That would imply that `"42px"` would be the ident with value "42px", written as `\34 2px` in CSS syntax. While we're not universal with it, we often do this sort of "the string is used literally" behavior precisely so you don't have nested escapes, with a CSS escape put in a JS string and thus needing to be JS-escaped as well. It's also slightly better perf to not invoke the parser unnecessarily. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7748#issuecomment-1312276414 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 12 November 2022 00:05:54 UTC