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

If no optional script is provided, there is no muting, at least in the new plan.

I guess you are right that browsers somehow determine the filename/colno/lineno even for UA-created scripts. Here is a simple example http://jsbin.com/mediwuwodu/edit?html,console. That is annoying... There's going to be some sort of algorithm that traces back to the nearest author code on the stack, or something. We should figure out how to spec that when we fix whatwg/html#958.

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