Closed
Bug 1130046
Opened 9 years ago
Closed 5 years ago
Clicking on errors in the console creates a new window instead of jumping to the debugger tab
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: simonzack, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 20150202183609 Steps to reproduce: Raise an exception in javascript, source maps produced using 6to5. Actual results: Clicking on errors in the console creates a new window. Expected results: Clicking on the error in the console should jump to the debugger window, it worked sometimes but often doesn't, even when I close the tab and restart it again. Btw, shouldn't there only be one way of viewing the source after clicking the line number?
I see what I did to jump to the debugger window, it was by unticking (not ticking) the show original sources tab. But I think that always jumping there is more consistent whether it's ticked or not.
Comment 2•9 years ago
|
||
I can confirm this. I do a lot of development with Meteor and CoffeScript, and clicking a link to a source file opens a new window. (Then there's the fact that Meteor errors are logged in a horrible format, but that's a Meteor problem, in fact what I'm working on right now.)
Comment 3•9 years ago
|
||
Apropos, the functionality in question was added via #766001, in case someone wants to check the leading discussion.
Updated•6 years ago
|
Product: Firefox → DevTools
Comment 4•5 years ago
|
||
this relates to the old debugger
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•