1309493 - When loading Sourcemaps, the console points to the wrong original source

Status: RESOLVED DUPLICATE of bug 1359144

(DevTools :: Console, defect, P2)

Description

[valepu]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20160922113459

Steps to reproduce:

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:49.0) Gecko/20100101 Firefox/49.0

Using an application with angular2, webpack and typescript such as https://github.com/shibbir/generator-angular2-typescript or https://github.com/AngularClass/angular2-webpack-starter (i don't know if this happens with other combinations of libraries / languages, sass sourcemaps are mapped correctly though)

1) Add a console.log somewhere in the code of a component (there are some already in these premade projects)

2) With the console open go to the main page and click on the line number in order to open the source code for that specific line

For more informations see http://stackoverflow.com/questions/39973108/sourcemap-not-working-on-firefox-with-webpack-on-angular-2-application


Actual results:

The source code line link is presented like this in the console

view-source:http://localhost:3000/app.js line 265 > eval

so when i click on it i end in a error page saying

 Cannot GET /app.js%20line%20265%20%3E%20eval

and i receive an alert saying 

The specified line was not found

(Though this is because the response is 1 line long and not the expected file)


Expected results:

The source code line link should've pointed to the correct .ts file from where the javascript code was generated.

This works correctly on chrome

Comment 1

[Loic]

Is it possible to create and attach a simple page as testcase to reproduce the issue? (or a Zip archive with files)

Comment 2

[valepu]

Sorry it took so long, i have set up a very simple test page: 

http://www.mjzone.net/moztest/#/my-comp

if you load the page with the console open you'll see a console.log "Test for Mozilla Sourcemaps", this will point to bundle.js (the minified file) on Mozilla but to component.ts (the original Typescript file) on Chrome (sometimes it will show bundle.js first because it's still loading sourcemaps)

Comment 3

[Tom Tromey :tromey]

That URL no longer works.

Comment 4

[valepu]

Fixed, sorry for the inconvenience

Comment 5

[Tom Tromey :tromey]

Thanks!  I tried it out.
This was fixed by bug 1359144, so I'm closing this as a dup.