Bug 137663 - Web Inspector: should be able to dump protocol traffic to console when remote inspecting
Summary: Web Inspector: should be able to dump protocol traffic to console when remote...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
Keywords: InRadar
Depends on: 151635
Blocks: InspectorDebug
  Show dependency treegraph
Reported: 2014-10-13 11:28 PDT by Brian Burg
Modified: 2016-12-13 15:35 PST (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Brian Burg 2014-10-13 11:28:27 PDT
This does nothing when remote inspecting:


So even if InspectorBackend is dumping protocol traffic, you can only see it in the second level inspector. This doesn't scale well if you need to look at large amounts of traffic or save it to a file for processing.

It would be great if we had some way to optionally forward console messages so they would be dumped on the desktop's stderr, rather than on an iOS device. A workaround is using InspectorFrontendHost.unbufferedLog to dump protocol messages, but it would be good to see other console output as well.

We could expose WebKit2LogsPageMessagesToSystemConsoleEnabled through InspectorFrontendHost, but it's not easy to tee the calls to console.log since it is implemented as a native method.
Comment 1 Radar WebKit Bug Importer 2014-10-13 11:28:42 PDT
Comment 2 Brian Burg 2014-10-18 17:00:07 PDT
I guess the inspector could forward console.log calls to InspectorFrontendHost.unbufferedLog (or something similar) if inspecting a remote target.
Comment 3 Brian Burg 2015-11-05 13:34:30 PST
Maybe the problem is that remote inspector is WK1, and it's a different pref. We have too many prefs.
Comment 4 Brian Burg 2015-11-28 00:07:32 PST
Adding dependency which will make it possible to implement a proxying protocol tracer.