Re: [csswg-drafts] [css‑syntax] `<string‑token>` should probably handle valid surrogate pairs (#6352)

Do you have a compat need for this? I'd prefer not to allow it if possible, as it would require us to either allow lone surrogates (the only way these can be produced, as they're otherwise "censored" away during parsing) or add some complication to escaping such that, if you decode a high surrogate, you immediately check if the next characters are an escape for a low surrogate, then decode them together and emit the combined codepoint.

That's *possible*, I'd just like to avoid it if it's not necessary.

----

I'm not sure what the significance of your comment about CSS1 only allowing 4-digit escapes is, sorry.

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


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

Received on Tuesday, 8 June 2021 01:12:04 UTC