NEW 137663
Web Inspector: should be able to dump protocol traffic to console when remote inspecting 
https://bugs.webkit.org/show_bug.cgi?id=137663
Summary Web Inspector: should be able to dump protocol traffic to console when remote...
Brian Burg
Reported 2014-10-13 11:28:27 PDT
This does nothing when remote inspecting: WebKit2LogsPageMessagesToSystemConsoleEnabled 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.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2014-10-13 11:28:42 PDT
<rdar://problem/18636166>
Brian Burg
Comment 2 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.
Blaze Burg
Comment 3 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.
Blaze Burg
Comment 4 2015-11-28 00:07:32 PST
Adding dependency which will make it possible to implement a proxying protocol tracer.
Note You need to log in before you can comment on or make changes to this bug.