1327011 - It's too easy to accidentally pause debugger and let it switch scripts and slow down debugging process for a minute

Status: RESOLVED DUPLICATE of bug 1552532

(DevTools :: Debugger, defect, P3)

Description

[arni2033]

>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509
STR_1:
1. Open   data:text/html,<script src="data:text/javascript,onclick=function(){}//.js"></script>
2. Black-box the script
3. Click "Click to pause" button in debugger
4. Click "Waiting for next execution"


AR:
 Step 3 - debugger switches to the mode when it expects for next script execution ("trap mode")
 Step 4 - no visible action
 
ER:  Either X or Y
 X) Step 4 - debugger should switch to the mode when all JS code can run freely ("normal mode")
 Y) There should be another way to easily switch to normal mode, and prevent
    scripts switching and useless actions required to exit "trap mode"


Explanation:
 Sometimes I end up in situation when I have many breakpoints, half of them disabled. And I need to
 just finish code execution. The only way I can do it is by constantly clicking "pause/resume" button,
 because I can't use "toggle breakpoints" button (some of breakpoints are disabled)
 
 However, after bug 789430 it's possible to accidentally fall into the trap.
 Use_case_1:
 When I constantly click "pause/resume" button and I successfully pass all breakpoints, debugger
 switches to "trap mode", when any action on the page (like mousemove) or a code that runs by schedule
 (setTimeout/setInterval) can switch debugger to another script/line far away from current script/line
 
 Basically, debugger forces me to do some useless action (e.g. click on the page) to exit "trap mode"
 and continue my debugging. This is psychologically difficult.
 So far, I found the following workaround:   Doubleclick on any line number in debugger.


Note:
 If you read explanation carefully, you probably noticed that expectation (X) doesn't help Use_case_1
 completely. That is one of the reasons why this bug is unconfirmed. I just don't know 3 things:
 (1) Is there a workflow that will be broken by expectation (X)
 (2) What is doable in debugger front-end
 (3) Is there any plan to fix said Use_case_1 and free user from doing "useless actions" (see above)
     Maybe debugger shouldn't switch to other script w/o user interaction and simply show breadcrumbs?
     That plus expectation (X) would fix any of my use cases.
     Probably there'll be a separate button/shortcut for "Click to pause"? I don't know that.

Comment 1

[:Harald Kirschner :digitarald]

Bug 1552532 help with this. Closing as this one doesn't have any immediate action (but a great description, thank you!)