Bug 97002
| Summary: | Web Inspector: console execution context is confusing when debugger is on a breakpoint | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andrey Kosyakov <caseq> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | apavlov, bweinstein, graouts, inspector-bugzilla-changes, keishi, loislo, mark.lam, pfeldman, pmuellr, rik, webkit-bug-importer, yurys |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | |||
| Bug Blocks: | 116924 | ||
Andrey Kosyakov
When paused on a breakpoint, inspector always evaluates console expressions in the context of selected call frame. When the breakpoint is in a subframe, this means the global object will be that of subframe. This may be confusing, given that we display "top frame" in the console evaluation context (and the debugger panel indicating a breakpoint may be off the screen, so user does not realize he's on a breakpoint).
I suggest that when paused, we display something like "<call frame>" as an option in the execution context selection combo box of the console, and let one change it to override the execution context to that of different global object (i.e. a different frame or world).
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/17898320>