Convert SetIsIncognitoProcess to use mojo.

chrome/common/renderer.mojom

Index: chrome/common/renderer.mojom
diff --git a/chrome/common/renderer.mojom b/chrome/common/renderer.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..50d7f7a004eb4bcf5396ec86dab7a09250c837b3
--- /dev/null
+++ b/chrome/common/renderer.mojom
@@ -0,0 +1,17 @@
+// Copyright 2016 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;
+
+// The primordial Channel-associated interface implemented by a render process.
+// This should be used for implementing browser-to-renderer control messages
+// which need to retain FIFO with respect to legacy IPC messages.
+interface Renderer {

[sky, 2016/12/05 16:11:22]

For an interface that is meant to contain control/configuration information this
name is very generic. Maybe RendererConfiguration?

[nigeltao1, 2016/12/08 04:33:41]

This (chrome.mojom.Renderer) is meant to be the s/content/chrome/ analog of the
existing content.mojom.Renderer interface. As rockot said in
https://groups.google.com/a/chromium.org/d/msg/chromium-mojo/sGmLgv-H28w/jx06...

"For one example there's the Renderer Channel-associated interface -- this is
just a bag of miscellaneous browser-to-renderer messages which have been
converted. It's accessible via RenderProcessHost::GetRendererInterface and is
safe to call into very early.

You could mimic this approach for messages like SetIsIncognitoProcess, but since
it's in the src/chrome layer you'll need to introduce a new interface and bind
it somewhere in the renderer".

That's exactly what I did.

+  // Configures the renderer, queued to send when the render process will
+  // launch.
+  //
+  // TODO(nigeltao): port the ChromeViewMsg_SetContentSettingRules legacy IPC
+  // message to be an additional arg here.
+  SetInitialConfiguration(bool is_incognito_process);
+};