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

I think it would be better that if someone does something fishy, like moving a scoped custom element from a ShadowRoot to the main Document, an error would be thrown (f.e. `DOMException: Scoped custom element does not belong to this Document or ShadowRoot`). I do not think that allowing weird patterns is ideal in general, in any language or system, if it can be avoided.

Because using Scoped Custom Element Registries is an opt-in feature, there is no harm / no breaking change in throwing errors for those rare cases, and honestly it will help people out by keeping their programs in states that make sense.

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