Merge lp://staging/~abreu-alexandre/oxide/donottrack into lp://staging/~oxide-developers/oxide/oxide.trunk

Bump Chromium rev to 45.0.2427.7

Persist media device permissions for the life of WebContext

Make ContentBrowserClient / ContentRendererClient memebers of ContentMainDelegate like ContentClient already is

Pass the application locale to ui::ResourceBundle::InitSharedInstanceWithLocale. Because we don't build with glib support, it's unable to detect the system locale and depends on a preferred one being passed

Convert UserScriptMaster in to a KeyedService

Create a single TestWebContext in tst_WebView_save_restore_state.qml

Don't allow QObjects to be passed to WebContextDelegateWorker

Add justifications around less-obvious uses of base::Unretained

Fix save/restore unit tests.

Bump Chromium rev to 45.0.2431.0

Fix an intermittent test failure

Ensure we have a WebScopedMicrotaskSuppression instance on the stack when we call in to V8

Add a basic editorconfig file - you can get editorconfig plugins for various editors from http://editorconfig.org/. This avoids having to turn on support for modelines, which is disabled in some editors (eg, vim) for security reasons

Some updates for the content script messaging:
- The payload is no longer converted to a string for the wire - instead, we use base::Value directly.
- As a consequence, on the renderer side, we now use content::V8ValueConverter to convert the payload from v8::Value to base::Value. This means we can get rid of the hacky script we compile for each script context, just to call JSON.stringify.
- On the browser-side, we now convert from base::Value directly to QVariant using a custom converter. There is no longer a dependency on QJsonDocument.
- As a hardening measure, our converter on the browser side protects against excessive recursion that would otherwise exhaust stack space.
- The "args" parameter for script messages is deprecated - use "payload" instead. "args" never really made sense as it implies it's always a list, and is there as a consequence of this API being put together in haste to get unit tests working.
- Message payloads no longer have to be JSON arrays or objects - they can be any primitive that can be represented in JSON.
- The script message dispatcher on the browser side is no longer a BrowserMessageFilter running on the IO thread, but instead a WebContentsObserver. We can do that now since it has an API to expose the source RenderFrameHost.

Use the preferred allow() method for the geolocation permission tests (we still retain one test for the deprecated accept() method though)

Store TestApiHost in TestWebView, keyed by WebFrame

Add TestUtils.waitFor, so that we can stop duplicating the same function for tests that don't use TestWebView

Bump depot_tools to c1ae89ecd635abfea2d94e5b49c7d92f49f28f22

Improve script messaging tests

LP: #1466208

Remove a spurious console.log

Correctly detect when we are running on Mir/Mesa

Assume that the display is already initialized

Bump Chromium rev to 45.0.2438.3

Add WebContext.userAgentOverrides API, which is a replacement for WebContext.userAgentOverrideDelegate. The new API allows applications to provide a list of regular expressions and user agent overrides as opposed to providing a JS worker that we call in to to ask for a user agent string. This allows us to stop relying on synchronous IPC to the browser

We can actually lazyily create UserAgentSettings. RenderProcessInitializer will create it when the first render process starts anyway

Fixes