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

> > One thing that's unclear from https://github.com/justinfagnani/scoped-custom-elements is that in which tree(s) existing unknown custom elements are upgraded in `define` call.
> 
> I believe each registry (`customElements` or new instances of `CustomElementRegistry`) will have it's own independent tree (or mapping tree) of element definitions. The trees would be differentiated according to the entity they are associated to. e.g. `customElements` is always associated to the Document and new registries need to be associated to a `ShadowRoot`.
> 
> FWIW, `define` should apply definitions this way. The problem goes within the distinction in the shadow root as you already described. Idk yet what would be the best solution here, maybe @justinfagnani and @caridy can help me out on this one.

I'm not sure I follow what you're saying. Multiple `ShadowRoot` can use a single custom / scoped `CustomElementRegistry` so it's unclear how it can have its own independent tree. It's more like a list of shadow trees but then the order in which those trees appear becomes a question. Presumably the order by which they're created because they don't necessary have any other well defined order.

-- 
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-677956862