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

I see. I guess from my perspective they are equally magical, in that in both cases the exception object is not created in the place given by filename/lineno/colno---in both cases it is created in C++, not in JS.

When I work on whatwg/html#958 I'll see if I can find a way to integrate this specific situation, or point out that it's special. Maybe it will even be natural to pass in the position of the constructor function. But I think this probably falls under the general area of there being not-great interop around filename/lineno/colno/error.stack.

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

Received on Monday, 29 August 2016 21:32:22 UTC