Re: [w3c/webcomponents] Add Scoped CustomElementRegsitry explainer (#865)

The other reason I like the idea that custom registries use the same tree walk as the global registry is that implementation optimizations will benefit both.

It's a good question what should happen when you move a shadow tree across documents. And losing the registry without recourse feels somewhat sloppy. Perhaps we need the equivalent of `adoptedCallback` for shadow roots so you get to recover somehow. (Alternatively we only support this on shadow roots created on ElementInternals so you can use `adoptedCallback` to recover.)

-- 
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/pull/865#issuecomment-700543131