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

Thank you for the pointer, I understand it's not easy to define "the relevant script" in generic way, but for custom elements, it is obvious, isn't it?

I think, at least in this case, the UA-created exceptions should indicate which constructor produced the invalid results. Otherwise developers would have hard time to figure out which custom elements failed. A colleague indicated we could embed such information into message, but it won't work with source map.

What about muted? The muted is defined against script IIUC, but the exception is not thrown by scripts. I guess we should copy the muted state of the script that returned invalid value, no?

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

Received on Monday, 22 August 2016 05:51:16 UTC