Re: [whatwg/dom] attachShadow default custom element registry (Issue #1407)

justinfagnani left a comment (whatwg/dom#1407)

@annevk

Huh, in STP 216 I see:

<img width="288" height="208" alt="Image" src="https://github.com/user-attachments/assets/e6302c67-ca8e-4286-87d7-2be912e304c5" />

Not seeing "Element C" would mean that it's broken.

> I don't really understand though how this is supposed to work though. The `my-x-b` instance's custom element registry will be `registryA`.

I'm saying that it should _not_ be `registryA` and that it should be the global registry.

> How would the browser figure out that the actual registry is something else?

No registry is set in `attachShadow()` so it should use the global registry.

> I guess what you're saying is that it would be easier for migration if we continued to use the global registry and then elements that did not want to use the global registry would specify an explicit registry in their attachShadow() call. But is that going to be the right answer long term as well?

Yes, it's always the right answer. The outer scope (the host's scope) should not change the inside scope. That's an implementation detail of the element that the outer scope is messing with. An element should always be able to rely on its registry.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1407#issuecomment-3353118732
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1407/3353118732@github.com>