Re: [w3c/webcomponents] CustomElements: upgrade runs connectedCallback on an element with a throwing constructor (#563)

> FWIW I think there may always be elements running around whose constructors threw, though; they can be created with 'new' which calls super(), discloses 'this', and then throws. We must continue to run callbacks for them because there's no effective way to detect them, that I know of.

Yeah. Such elements aren't failed; they're just elements with weird constructors, I guess. This is an inevitable consequence of us handing the constructor over to developers instead of using a createdCallback design.

-- 
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/563#issuecomment-245760132