Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)

@matthewp those are very good questions that need concrete answers.

As far as I can tell, the first example will create an instance of `HTMLUnknownElement` since the global registry hasn't claimed it. If eventually, after the insertion of the element, the custom element is registered, it could be upgraded (from the global registry, or from a local registry).

The second example is more generic, it could be simplified to just asking what happen when you insert an already upgraded element into a different shadow or global? IMO, since the shadow dom is not really a security mechanism, it will work just fine. Meaning that the scoped registry is about facilitating the upgrading process rather than a security boundary.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/716#issuecomment-369372020