Community
Participate
Working Groups
1. Open some looped JavaScript. 2. Set the breakpoint in the JS so it is hit on each loop cycle. 3. Start that JS script in debugger. 4. When the breakpoint is hit for the first time toggle "Skip all breakpoints" button. 5. Resume the script. 6. Untoggle the "Skip all breakpoints". "Progress information" dialog with generic "Operation in progress" message will be shown as soon as breakpoint is hit. The dialog won't complete and Cancel button won't close it. I found to way to access UI after this dialog is shown. Disabling/Enabling or Removing/Adding the breakpoint while script is running won't reproduce the problem.
We cannot reproduce this (tested on Win32 and Mac OS X). If you are still seeing this issue with the latest ATF milestone, please provide the exact test case that you are using.
Closing this bug as WORKSFORME. Eugene, if you can provide us with a small testcase that still demonstrates this issue, then please reopen this bug and attach the testcase.
Created attachment 78415 [details] Zipped test project
I can reproduce it in 0.2.3 v200709101650 1. Set a breakpoint in script.js#4 2. "Debug in Mozilla" page.html 3. When the breakpoint is hit, toggle "Skip All Breakpoints" on the Breakpoints view toolbar. 4. Continue the application. 6. Give it 15-30 seconds to run and untoggle "Skip All Breakpoints". This is not 100% reproducible but I can reproduce it approx. once for 3 runs.
