Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)

@ja-y-son commented on this pull request.



> -       <var>document</var>'s <a>effective global custom element registry</a>.
+       <var>inclusiveDescendant</var>'s <a for=Element>custom element registry</a> based on the
+       following conditions:
+
+        <ol>
+         <li><p>If <var>inclusiveDescendant</var>'s <a for=tree>parent</a> is null or
+         <var>inclusiveDescendant</var>'s <a for=tree>parent</a> is a {{DocumentFragment}} but not
+         a {{ShadowRoot}}, then set <var>inclusiveDescendant</var>'s
+         <a for=Element>custom element registry</a> to <var>document</var>'s
+         <a>effective global custom element registry</a>.
+
+         <li><p>If <var>inclusiveDescendant</var>'s <a for=tree>parent</a>'s
+         <a for=Element>custom element registry</a> is null or is equal to <var>document</var>'s
+         <a>effective global custom element registry</a>, then set <var>inclusiveDescendant</var>'s
+         <a for=Element>custom element registry</a> to <var>inclusiveDescendant</var>'s
+         <a for=tree>parent</a>'s <a for=Element>custom element registry</a>.

Updated to use "effective global custom element registry" strategy as discussed. Was trying to see if I could get the point across with another approach but it seems like "effective global custom element registry" is still the better way to go. Lmk if I'm missing anything on this idea.

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

Message ID: <whatwg/dom/pull/1437/review/3530535375@github.com>