On Mon, May 20, 2013 at 4:24 PM, Jim Blandy wrote:
> On 05/20/2013 01:03 PM, Peter van der Zee wrote:
> > This may not be the right place, but what should browsers do when an
> > is raised in an area of the translated code? As a dev I would not like to
> > be sent to a wild goose chase, only to find out later that the error
> > due to my code but due to the way it was translated.
> I don' think there's any way the browser can distinguish these two
> cases, even if source maps could be changed to help.
This isn't an issue for the SourceMap spec, but I would love to see a
side-by-side. Then if there's a translation error, the end user can more
easily see the problem and report the bug to the compiler project (and work
It's a tricky UI problem, though, due to inlining and so on.