Re: [w3c/webcomponents] Expose shadowRoot on element internals (#871)

Thanks for digging that up @mfreed7! And yeah, as @bathos shows we did in fact add the opt-out.

@rniwa until `define()` is called there is no definition for the element, right? `attachInternals()` will throw if that's the case. So that case is already covered as far as I can tell.

Being able to call `attachInternals()` makes you pretty powerful already. The main question is whether that power should be equivalent to shadow tree access. Again, that might well be okay. I just want everyone to be conscious of the implications.

-- 
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/871#issuecomment-675821466