925569 - Console errors shouldn't trigger "pause on exceptions"

Status: RESOLVED INVALID

(DevTools :: Debugger, defect, P3)

Description

[Tom Herold]

Attachment: screencast2.gif

If I write faulty and wrong commands in the JS console and have the "pause on exception" feature enables code execution will be stopped and dev tools will switch to the debugger view. However, in the debugger view I see the last open file and have no idea/no method of checking the console code that failed.

I would either expect that 1) I doesn't stop at all and logs the error to the console or 2) stops but shows me the right code in debugger.

I attached a short screencast of this behavior.

Comment 1

[Mihai Sucan [:msucan]]

I can confirm the bug.

Panos, is there a way we can avoid pause on exception for the console? maybe based on a custom eval source location?

Comment 2

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

Once we have bug 905700 fixed, we will be able to show users the eval'd code from the webconsole and you won't be paused at a hidden source anymore.

Aside: that's a pretty nifty gif, how'd you make it?

Comment 3

[Tom Herold]

(In reply to Nick Fitzgerald [:fitzgen] from comment #2)
> Once we have bug 905700 fixed, we will be able to show users the eval'd code
> from the webconsole and you won't be paused at a hidden source anymore.
> 
> Aside: that's a pretty nifty gif, how'd you make it?

@fitzgen: Sorry for the late reply. The tool is called LICEcap: https://github.com/lepht/licecap

Comment 4

[David Walsh :davidwalsh]

This is no longer an issue with the new debugger.