Convert ChromeViewMsg_SetAllowRunningInsecureContent to use mojo.

chrome/common/insecure_content_renderer.mojom

Index: chrome/common/insecure_content_renderer.mojom
diff --git a/chrome/common/insecure_content_renderer.mojom b/chrome/common/insecure_content_renderer.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..7685632d593562938bc8735c629db32ed3982273
--- /dev/null
+++ b/chrome/common/insecure_content_renderer.mojom
@@ -0,0 +1,12 @@
+// Copyright 2017 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+module chrome.mojom;
+
+// Renderers of possibly insecure mixed-content.
+interface InsecureContentRenderer {
+  // Sent to allow or forbid the running of insecure mixed-content. It may also
+  // reload the frame afterwards.
+  SetAllowRunningInsecureContent(bool allow, bool reload_frame);

[Sam McNally, 2017/02/03 17:36:58]

These parameters seem unnecessary; the renderer can correctly predict their
values. Can we get rid of them?

[nigeltao1, 2017/02/04 06:29:10]

Done.

+};