1407971 - Debugger functionality broken or radically altered in 56.0.1

Status: RESOLVED FIXED

(DevTools :: Debugger, defect)

Description

[Andy Robinson]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce:

Automatic upgrade to 56.0.1; Load application in development; Attempt to set breakpoints and debug


Actual results:

* Left pane code selection is collapsed requiring extra steps to find code
* Setting breakpoint may stop execution, but focus does not move to debugger
* Controls not visible without opening another pane on right
* Controls (play, step, step into, step out of, etc.) are not visually accentuated as before when breakpoint is active (e.g., blue play/resume button)
* Controls do not appear to function (step forward does not cause code pointer to move), though PLAY does seem to resume normal execution


Expected results:

All behaviors should have been identical to previous release.

Comment 1

[Jason Laster [:jlast]]

Hi Andy, thanks for pointing out some of the differences with the new UI

Some things are intentional and others are not.

* Left pane code selection is collapsed requiring extra steps to find code

> the default should be to have both panes open, if that's not the case we can fix it

* Setting breakpoint may stop execution, but focus does not move to debugger

> it should, if it doesn't that's a bug

* Controls not visible without opening another pane on right

> the default should be to have both panes open, if that's not the case we can fix it. We should also expand the right sidebar if it is collapsed and you're paused. I'll create a bug for that.

* Controls (play, step, step into, step out of, etc.) are not visually accentuated as before when breakpoint is active (e.g., blue play/resume button)

> we are working on making them more clear now :)

* Controls do not appear to function (step forward does not cause code pointer to move), though PLAY does seem to resume normal execution

> it should. can you share some examples?