- From: Darien Maillet Valentine <notifications@github.com>
- Date: Mon, 03 Jan 2022 11:39:45 -0800
- To: whatwg/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 3 January 2022 19:39:57 UTC
> So the choice here is really a statement about valid Web IDL files, I guess? Yep. It’s totally removed from any kind of observable web platform behavior. If curious, the background for why I noticed it is that I added new API surface to my parser which accepts JS string values (interpreted Web IDL source text). Previously it only read well-formed UTF-8 buffers, so USVs were a given, but now it was something I had to consider\*. At first I thought lone surrogates should probably pass through the lexer fine if appearing in in `string`, `comment`, or `other` tokens given what’s written, but then I caught the implication for USV string literal interpretation. > \* by “had to consider,” I mean I definitely did not have to consider it. i’m the only person using the parser in question and obviously I’m not gonna pass in any unpaired surrogates. but if i don’t invent problems, who will?? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/webidl/issues/1080#issuecomment-1004312761 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/webidl/issues/1080/1004312761@github.com>
Received on Monday, 3 January 2022 19:39:57 UTC