Bug 37456
| Summary: | Web Inspector: shortcut for marking a timeline | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Evan Martin <evan> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | bweinstein, joepeck, keishi, pfeldman, pmuellr, rik |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Evan Martin
We have console.markTimeline() for marking a point on the timeline.
Aside from that being impossible to discover ;) sometimes I'm trying to analyze the timing of something that involves a complicated set of nested menus where focus matters, or a somewhat difficult-to-reproduce state, or *something* (I can't exactly remember the circumstance, but it somehow feels common to me) where I hit record, spend some time fiddling with the page, and then cannot find where the interesting action is.
What I would like is to be able to dynamically mark points on the timeline via a shortcut key. It is important to grab the key such that the page is unaware you pressed it. Perhaps there are more general ways you could make it trigger that would make sense, like "don't record until the first relayout happens" or something.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Patrick Mueller
Should we have just one shortcut key that generates a timeline marker, with a message like "generated from shortcut"?
What kind of shortcut can we use that 1) doesn't get grabbed the system, and 2) wouldn't be sent to the browser anyway? If there are no such shortcuts available, perhaps we prompt the user for the shortcut key to use, or only enable a simple to capture shortcut key when the user enables that functionality via a toggle.
Timothy Hatcher
We likely will need to reserve the keyboard shortcut and hsow it in the browser (like Safari's Develop menu) to make it work.
Brian Burg
Closing as invalid, as this bug pertains to the old inspector UI and/or its tests.
Please file a new bug (https://www.webkit.org/new-inspector-bug) if the bug/feature/issue is still relevant to WebKit trunk.