- From: Philip Jägenstedt <notifications@github.com>
- Date: Wed, 11 Mar 2026 04:35:45 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 11 March 2026 11:35:49 UTC
foolip left a comment (whatwg/dom#1454) Thanks @annevk! Always using the HTML parser is straightforward in spec and implementation, the only thing that's not ideal about is that the more lenient parsing of `<?xml-namespace?>` may affect non-browser tooling. Basically what @zcorpan said, "I assume some folks would be upset if browsers start to use an HTML parser to parse the `xml-stylesheet` pseudo-attributes in XML documents." With a bespoke parser, that's mostly straightforward with "[collect a sequence of code points](https://infra.spec.whatwg.org/#collect-a-sequence-of-code-points)", but is there a way to decode character entities in attribute values that doesn't duplicate all of the tokenizer states character entities? Or could we do something simpler that ends up diverging slightly from how regular attribute values are parsed? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/1454#issuecomment-4038606346 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/pull/1454/c4038606346@github.com>
Received on Wednesday, 11 March 2026 11:35:49 UTC