Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525)

Hmm, so if I am understanding, the idea is to introduce some kind of test, and:

- If there is an element queue in the custom element reactions stack, store some kind of "throw an exception reaction" in the queue
- If there is no element queue in the custom element reactions stack, report the error
- When running custom element reactions at the end of a [CEReactions] algorithm, shuffle all "throw an exception reaction"s to the back of the queue (after all other reactions), and throw the first one of them?

This has the advantage of not causing throws in the middle of algorithms that might not expect it (which could help #512) but seems like a lot of complication...

---
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/525#issuecomment-227308892