Bug 185190
| Summary: | Web Inspector: selectively ignore debugger statements | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Frazer <frazer> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | bburg, inspector-bugzilla-changes |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
Frazer
In the same way a user can TURN ON break points, or add conditions to breakpoints,
may I suggest being able to add conditions to debugger statements or disable them individually?
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Blaze Burg
(In reply to Frazer from comment #0)
> In the same way a user can TURN ON break points, or add conditions to
> breakpoints,
> may I suggest being able to add conditions to debugger statements or disable
> them individually?
What is the use case that this enables, which is not currently possible? Can't you just add breakpoints if you don't want `debugger` to always pause?
This would be a nontrivial project as `debugger` compiles into a byte code that pauses the debugger. It is not really related to the existing breakpoints system.