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.
I guess the inspector could forward console.log calls to InspectorFrontendHost.unbufferedLog (or something similar) if inspecting a remote target.
Maybe the problem is that remote inspector is WK1, and it's a different pref. We have too many prefs.
Adding dependency which will make it possible to implement a proxying protocol tracer.