Bug 59119
| Summary: | Web Inspector: excluding scripts from a debugging session | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Pavel <pavel.genevski> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | apavlov, bburg, bweinstein, joepeck, keishi, loislo, pfeldman, pmuellr, rik, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Pavel
While debugging some complex code, especially one that makes heavy use of prototype.js, it would be useful if the user can exclude some scripts from the session. It shall work like this:
- assume the debugger has already stopped at a breakpoint that is not in an excluded script and the user is stepping in/over
- when the execution goes to an excluded script, the debugger shall step in automatically until a non-excluded file is encountered and then it shall stop, letting the user step manually again
- how to specify that a script shall be excluded
- option 1: while debugging, when the user encounters a script they are not interested in, they shall be able to click a button or right-click and select "Exclude"
- option 2: the user may specify this before they start stepping, by selecting the script and clicking a button
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Blaze Burg
*** This bug has been marked as a duplicate of bug 17240 ***