Bug 26801
| Summary: | when paused in the debugger, no web pages will load in other tabs | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Patrick Mueller <pmuellr> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ap, bburg |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Patrick Mueller
If you've paused in the debugger by hitting a breakpoint, and perhaps stepping through some code, but are in any case "paused", sessions in other tabs of the window you are debugging are also paused, to some extent.
The most noticeable effect is that traversing links, or entering locations in the location bar appear to "hang". If you go to the debug window and get the debugger into a "running" state instead of "paused", the actions requested on the other tab windows will complete.
I don't know how many times this has hit me, thinking my network connection must be dead.
One of the following should actually happen:
- fix the problem so the other tab windows aren't paused
- if the problem can't be fixed, then a (highly) visible indicator should be provided on the confusingly "paused" windows, mentioning the fact that the windows are paused because the debugger is paused. Presumably with a link that will take you directly to the paused debug window so you can "fix" the problem yourself (press "Go").
I haven't tried to see if pages in other windows are paused, and what the affects of having multiple debug windows open are, but these should be investigated as well.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Timothy Hatcher
This is pretty much by design, since other pages in other windows can be in communication with the paused JS. There might be ways for us to clearly say some pages are not like this though.