- From: Philip Jägenstedt <notifications@github.com>
- Date: Mon, 09 Mar 2026 15:34:41 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/pull/1454/review/3918616534@github.com>
@foolip commented on this pull request.
> +<div algorithm>
+<p>To <dfn>update attributes from data</dfn> for a {{ProcessingInstruction}} <a for=/>node</a>
+<var>pi</var>:
+
+<ol>
+ <li><p><a for=map>Clear</a> <var>pi</var>'s <a for=ProcessingInstruction>attribute map</a>.
+
+ <li><p>Let <var>context</var> be the result of <a>creating an element</a> given
+ <var>pi</var>'s <a>node document</a>, "<code>html</code>", and the <a>HTML namespace</a>.
+
+ <li><p>Let <var>markup</var> be the concatentation of "<code><attrs </code>",
+ <var>pi</var>'s <a for=CharacterData>data</a>, and
+ "<code>></attrs></code>".
+
+ <li><p>Let <var>fragment</var> be the result of invoking the
+ <a>fragment parsing algorithm steps</a> with <var>context</var> and <var>markup</var>.
I've handled the exception now with "If this throws an exception, then return."
I'm definitely open to using a single parser or switching based on some other condition, but the dual constraints of preserving current XML behavior and allowing for HTML syntax in HTML led to the current approach.
--
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/1454#discussion_r2908285891
You are receiving this because you are subscribed to this thread.
Message ID: <whatwg/dom/pull/1454/review/3918616534@github.com>
Received on Monday, 9 March 2026 22:34:45 UTC