|Summary:||Web Inspector: inspect Web Sockets in the new Resources panel rather than Network Log.|
|Product:||WebKit||Reporter:||Pavel Feldman <firstname.lastname@example.org>|
|Component:||Web Inspector (Deprecated)||Assignee:||Yuta Kitamura <email@example.com>|
|Severity:||Normal||CC:||firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com|
|Version:||528+ (Nightly build)|
Now that we have dedicated panel for resources, we should inspect Web Sockets there (i.e. have dedicated Web Sockets group with live web sockets under it). They did not fit the old resources panel well (which is now network log) since they had different timeline nature.
Created an attachment (id=72934) [details] UI mock-up for WebSockets in new Resources panel I created a UI mock-up for new Resources panel. As this is just a mock, please disregard inconsistencies of domain name and file names. (And please forgive my poor gimp skills...) I'm planning to: - Add WebSocket resource tree. - Show ResourceView when a WebSocket resource is selected. What do you think about this plan? Suggestions?
There was recent addition of WebSocket data to the Network panel. Change: http://trac.webkit.org/changeset/115427 Write-Up: http://updates.html5rocks.com/2012/05/Websocket-Frame-Inspection-now-in-Chrome-DevTools A more general summary of the data in the Resource panel does sound useful though.