Bug 147066 (InspectorDebug)

Summary: [META] Make it easier to debug the Web Inspector
Product: WebKit Reporter: Brian Burg <burg>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: graouts, inspector-bugzilla-changes, jjgjoojis, jonowells, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
See Also: https://bugs.webkit.org/show_bug.cgi?id=147073
Bug Depends on: 115579, 135779, 137663, 144132, 147068, 147069, 147438, 148481, 148802, 151268, 151714, 151922, 151958, 151959, 152136, 158056, 158099, 135467, 135588, 141083, 141742, 148088, 148750, 151151, 151581, 151635, 151923, 152671, 158055    
Bug Blocks:    

Description Brian Burg 2015-07-18 12:49:25 PDT
Tracking bug for all improvements to inspector debuggability.
Comment 1 Radar WebKit Bug Importer 2015-07-18 12:49:45 PDT
<rdar://problem/21888703>
Comment 2 BJ Burg 2015-11-27 17:36:03 PST
Over vacation I've been tackling some of these productivity-sapping bugs. With the most egregious ones out of the way, I'm looking at specialized tools for engineering builds only:

 * ability to persistently enable a setting to capture protocol messages
 * ability to save and export protocol traffic within Web Inspector
 * new tab and content views to visualize or otherwise understand protocol messages
    - wall-clock linear view
    - two-column view, with requests on the left and responses on the right (with arrows to connote message sends).
    - hyperlinks / secondary selections for related messages (i.e., request and response)
    - sort by initiator, RTT duration, dispatch duration, etc.

 * ability to send captured protocol traffic from inspector^1 to inspector^2. This enables awesome stuff:
    - linkifying log spam and making it easier to read
    - integrate protocol message data into a custom Instruments timeline