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

Agreed that it should not run.

These were moved early in the algorithm by https://github.com/whatwg/html/pull/1366 for the reasons explained there. Given those reasons, I am not sure there is an elegant patch here where we avoid queuing in this sort of scenario. Probably the best solution is to just insert a "is not failed" check inside "invoke custom element reactions".

Hmm. Or maybe whenever we set the state to failed, we empty the element's custom element reaction queue.

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