Code review comment for lp:~abreu-alexandre/webbrowser-app/devtools-support

> When doing this I basically had 2 use cases in mind:
>
> - the webbrowser-app/webapp-container being launched in a debug mode,
>
> - an application (third party) using the ubuntu webview and one wanting to
> "black box" debug it w/o having to touch it (either because one cannot or
> should not). I was thinking mostly QA needs to AP test UI componenets that use
> the UbuntuWebView w/o having to touch it. They would need a way to turn on the
> devtools w/o having access to the app itself, before being able to drive it w/
> selenium etc.
>
> In that context, some sort of an env var seemed ok to me,

I guess that makes sense. One thing I just noticed is that oxide allows us to specify only a numerical port, no host. I guess it means we cannot connect to a webview running on a different device? With QtWebKit, we were able to connect to a webview running on a phone from a separate desktop machine.