Re: [w3c/webcomponents] Returning a Proxy from a Custom Element constructor (#857)

> If that target were still the object users dealt with, your proxy would just be disappearing into the ether.

What I meant is, the underlying target of the Proxy my custom element users have is the same this that the engine has, and that instance isn't going anywhere. Can't the engine be made to access it?

-- 
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/857#issuecomment-560015637