Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)

@annevk commented on this pull request.



> @@ -6018,12 +6006,14 @@ these steps:
     <ol>
      <li><p>Set <var>inclusiveDescendant</var>'s <a for=Node>node document</a> to <var>document</var>.
 
-     <li><p>If <var>inclusiveDescendant</var> is a <a for=/>shadow root</a> and
-     <var>inclusiveDescendant</var>'s <a for=ShadowRoot>custom element registry</a>
-     <a>is a global custom element registry</a>, then set <var>inclusiveDescendant</var>'s
-     <a for=ShadowRoot>custom element registry</a> to <var>document</var>'s
-     <a>effective global custom element registry</a>.
-
+     <li><p>If <var>inclusiveDescendant</var> is a <a for=/>shadow root</a>:
+      <ol>
+        <li>If <var>inclusiveDescendant</var>'s <a for=ShadowRoot>custom element registry</a>
+        <a>is a global custom element registry</a> or null, then set <var>inclusiveDescendant</var>'s
+        <a for=ShadowRoot>custom element registry</a> to <var>document</var>'s
+        <a>effective global custom element registry</a>.

Does that mean we can remove "keep custom element registry null" completely? I think it's only used for this.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/1423#discussion_r2540698144
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/pull/1423/review/3481005643@github.com>