| Summary: | Web Inspector: DebuggerManager sends spurious setBreakpointsActive commands when setting a breakpoint | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Brian Burg <burg> | ||||||
| Component: | Web Inspector | Assignee: | Brian Burg <burg> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | commit-queue, graouts, joepeck, timothy, webkit-bug-importer | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | 528+ (Nightly build) | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Attachments: |
|
||||||||
Created attachment 236193 [details]
Patch
Turns out it was just a typo. Comment on attachment 236193 [details]
Patch
r=me
Comment on attachment 236193 [details] Patch Clearing flags on attachment: 236193 Committed r172217: <http://trac.webkit.org/changeset/172217> All reviewed patches have been landed. Closing bug. |
Created attachment 236145 [details] partial protocol dump For every Debugger.setBreakpoint command, we also send Debugger.setBreakpointsActive and Debugger.setPauseOnExceptions commands, even if nothing changed. This adds a lot of useless messages in the initialization sequence, and for all further breakpoint sets.