Move ViewHostMsg_CreateWindow to mojom

third_party/WebKit/public/platform/referrer.mojom

+// 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 blink.mojom;
+
+import "url/mojo/url.mojom";
+
+// Maps to blink::WebReferrerPolicy in
+// src/third_party/WebKit/public/platform/WebReferrerPolicy.h.
+//
+// TODO(rockot): Update all WebReferrerPolicy consumers to use this type
+// instead, and remove the typemap.
+enum ReferrerPolicy {
+    ALWAYS,
+    DEFAULT,
+    NO_REFERRER_WHEN_DOWNGRADE,
+    NEVER,
+    ORIGIN,
+    ORIGIN_WHEN_CROSS_ORIGIN,
+    NO_REFERRER_WHEN_DOWNGRADE_ORIGIN_WHEN_CROSS_ORIGIN,
+};
+
+// This struct holds a referrer URL, as well as the referrer policy to be
+// applied to this URL. When passing around referrers that will eventually end
+// up being used for URL requests, always use this struct.
+struct Referrer {

[dcheng, 2016/09/27 23:09:42]

It's a little surprising to me that we define this in public/platform, when it's
only created and consumed in content. Is there somewhere else it would end up
being used in Blink?

[Ken Rockot(use gerrit already), 2016/09/28 00:20:05]

We could define it in content instead if you prefer. I guess my expectation is
that many interfaces which use it will eventually be consumed directly from
blink code, so this would very likely move to blink anyway. It feels like a web
platform concept.

[dcheng, 2016/09/28 00:30:51]

Perhaps, but it would be easy enough to move it into the appropriate layer then.

[Ken Rockot(use gerrit already), 2016/09/28 01:15:24]

As discussed off thread, leaving this here for now since it's kind of weird no
matter where it goes (splitting mojom Referrer from mojom ReferrerPolicy is
weird, but splitting mojom ReferrerPolicy for WebReferrerPolicy is also weird).

+esprehn for opinion here

+  url.mojom.Url url;
+  ReferrerPolicy policy;
+};