Bug 10929
| Summary: | WebKit could benefit from a tool to observe/debug event dispatch | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Enhancement | CC: | ap, aroben, joepeck, mrowe, timothy |
| Priority: | P4 | Keywords: | InRadar |
| Version: | 420+ | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
Eric Seidel (no email)
WebKit could benifit from a tool to observe/debug event dispatch
bdash and I just spent a while talking about JS/Web tools that we'd like to see to better support web developers using Safari/WebKit. One idea which came out of this discussion was for a tool to track javascript event dispatch.
I have had a number of cases where I've had to debug mouse-events for my web-application in Safari and been frustrated by having to resort to gdb to do this tracking. It would be nice if there were a way to easily see a log of all attempted dispatch, or to have information a priori as to where a mouse event might be captured/targeted.
Wiring this sort of tool into WebKit should be relatively straightforward. A couple hooks into EventTargetNode::dispatchGenericEvent should do the trick. The larger question (to me) is what would such a tool look like.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
David Kilzer (:ddkilzer)
<rdar://problem/5762056>
Timothy Hatcher
*** Bug 17430 has been marked as a duplicate of this bug. ***
Joseph Pecoraro
The Timeline Panel helps with this, but usability on these types of use cases could probably still improve.
Timothy Hatcher
Not great, but the console has support for Firebug's monitorEvents(<element>, [<event type>, ...]).
Timothy Hatcher
The Timeline panel is the answer for this.