147066 InspectorDebug 2015-07-18 12:49:25 -0700 [META] Make it easier to debug the Web Inspector 2026-01-12 09:03:46 -0800 1 1 1 Unclassified WebKit Web Inspector 528+ (Nightly build) All All NEW https://bugs.webkit.org/show_bug.cgi?id=147073 InRadar P2 Normal --- 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 1 burg webkit-unassigned graouts inspector-bugzilla-changes jjgjoojis jonowells webkit-bug-importer oldest_to_newest 1110369 0 burg 2015-07-18 12:49:25 -0700 Tracking bug for all improvements to inspector debuggability. 1110370 1 webkit-bug-importer 2015-07-18 12:49:45 -0700 <rdar://problem/21888703> 1144618 2 bburg 2015-11-27 17:36:03 -0800 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