Closed Bug 1420381 Opened 7 years ago Closed 5 years ago

Clicking the script location on a console message do not open the debugger

Categories

(DevTools :: Console, defect, P3)

58 Branch
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: udon, Unassigned)

Details

(Keywords: regression, regressionwindow-wanted)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20171120142222

Steps to reproduce:

Any script error that is logged to the console.


Actual results:

The auto-linking/linkification to the right of the reported error shows the offending script name, line number and character as normal. In Firefox Developer Edition (58.0b5 (64-bit)) clicking on the line number does not take you to the offending line in Debugger. Repeating the process in Firefox Quantum (57.0 (64-bit)), same page/script error, click on the line number takes you to the offending line of script in Debugger.


Expected results:

Clicking on the line number should take you to the line of the script in Debugger.
Component: Untriaged → Developer Tools: Console
Summary: console auto-linking no longer working → Clicking the script location ona console message do not open the debugger
udon, could you give us a link / a test case so we can investigate what is going on ?
Flags: needinfo?(udon)
Summary: Clicking the script location ona console message do not open the debugger → Clicking the script location on a console message do not open the debugger
A plain HTML page with a deliberate JS error:
https://s.codepen.io/chopstik/debug/wPxLqm/XxkVwDxVbpvM
Flags: needinfo?(udon)
https://codepen.io/chopstik/pen/wPxLqm/ for the full pen
Thanks udon ! 

An initial investigation reveals that sources with SyntaxError are not fetched by the debugger. 
Then, in the console, we try to open the debugger, but can't find the file, so we default to show the "view source" page.

I filed https://github.com/devtools-html/debugger.html/issues/4798 to fix this in the debugger.
Product: Firefox → DevTools
Priority: -- → P3

This looks like this is fixed in Firefox Nightly :)

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.