Console error link to code line not taking you to code line
Categories
(DevTools :: Console, defect, P2)
Tracking
(Not tracked)
People
(Reporter: asunada, Unassigned)
References
Details
Attachments
(1 file)
2.48 MB,
video/quicktime
|
Details |
Thank you for helping make Firefox better. If you are reporting a defect, please complete the following:
What were you doing?
Please tell us what site you were on, and what steps led to the error you are reporting
- I was building an app on my local machine at localhost:8888
- An error appeared in the console and I clicked the link to the code line that failed
- Nothing happened. I was not redirected.
What happened?
Browser did not crash. Nothing happened other than the dev tools not directing me to the code line.
What should have happened?
I should have been directed to the line of code in the "debugger" tab in developer tools
Anything else we should know?
This seems to happen in all console notifications for me in firefox nightly. This DOES NOT seem to happen in the standard firefox browser, ONLY in nightly
Comment 1•6 years ago
|
||
Thanks for the report and the video, Andrew!
This might be related to bug 1565485. Can you check Browser Console for errors and see if anything debugger related pops up?
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to :Harald Kirschner :digitarald from comment #1)
Thanks for the report and the video, Andrew!
This might be related to bug 1565485. Can you check Browser Console for errors and see if anything debugger related pops up?
It might be related! The behavior in that bug shows that the console itself isn't showing up at all, however. My experience was that the console did actually show up and showed me the errors. However, when I went to click on the error like I showed in the video, nothing happened. Those don't seem like the same bug to me.
Comment 3•6 years ago
|
||
The behavior in that bug shows that the console itself isn't showing up at all
My understanding is that the debugger doesn't show up, which is what show up when you click the source links in the Console.
You can open the Browser Console with Cmd/Ctrl-Shift-J (https://developer.mozilla.org/en-US/docs/Tools/Browser_Console#Opening_the_Browser_Console) and see if you have a similar error.
Reporter | ||
Comment 4•6 years ago
|
||
(In reply to :Harald Kirschner :digitarald from comment #3)
The behavior in that bug shows that the console itself isn't showing up at all
My understanding is that the debugger doesn't show up, which is what show up when you click the source links in the Console.
You can open the Browser Console with Cmd/Ctrl-Shift-J (https://developer.mozilla.org/en-US/docs/Tools/Browser_Console#Opening_the_Browser_Console) and see if you have a similar error.
Oh, no you're right. My debugger is not showing up, and the console line link is just not working as a symptom of that error.
I feel like this is but will likely get remedied when the debugger bug gets fixed. I think it could be worth it maybe to just add this error as part of the debugger bug.
Comment 5•6 years ago
|
||
Let's see if this get fixed when Bug 1565485 lands
Updated•6 years ago
|
Reporter | ||
Comment 7•6 years ago
|
||
I am not. It seemed to actually be an issue with the scripts tab not working in general. I believe it's been fixed since then.
Description
•