Re: [w3c/webcomponents] Make createElement report an exception instead of propagating an exception (#569)

There are two possibilities:

1. keep using the sync flag, try/catch the exception, report it, and return HTMLUnknownElement like the parser does
2. use upgrade-like semantics and [CEReactions]

The observable differences here are subtle and minimal. (1) will return HTMLUnknownElement; (2) will return HTMLElement. And then there's the subtle constructor-vs.-upgrade issues, mostly around error cases.

I don't have a strong preference. I think @rniwa was leaning toward (1). It would be good for someone (probably me, maybe I can get @dominiccooney to do it) to enumerate all the differences in more depth, just to be sure there isn't a clear winner hiding there.

-- 
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/569#issuecomment-247990232