Clicking on errors in the console creates a new window instead of jumping to the debugger tab

UNCONFIRMED
Unassigned

Status

UNCONFIRMED
4 years ago
4 months ago

People

(Reporter: simonzack, Unassigned)

Tracking

36 Branch
x86_64
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
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?
(Reporter)

Updated

4 years ago
Component: Untriaged → Developer Tools: Debugger
(Reporter)

Comment 1

4 years ago
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

3 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

3 years ago
Apropos, the functionality in question was added via #766001, in case someone wants to check the leading discussion.

Updated

4 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.