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

> So how well established are the requirements? In terms of supporting multiple shadow roots, documents, etc. And by registration cost do you mean define/upgrade cost? It seems that running JavaScript would easily be the most expensive there. (Not saying that we should accept large tree walks if we can avoid them, but consistency and simplicity in the high-level design are also worthy goals.)

If moving a shadow root with a scoped registry is more of an edge case, then we could also consider not upgrading anything that moved to another document and only consider shadow roots that are connected to the same document. That would allow us to keep the algorithm simple & similar.


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