Re: [w3c/webcomponents] "The problematic position" when Custom Elements throw errors? (#547)

The demo still has the JS that calls UA code to cause the exception, so Blink uses the caller JS. I guess it's not so hard for other browsers too, if the caller had try/catch, it should catch the UA-created exception, so UA must know the caller context.

In custom elements. when the parser calls the constructor, there's no JS that calls the UA code, so we needed the special casing. I'm not sure if there are such cases already in the spec, at least I could not find any.

-- 
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/547#issuecomment-241610980