Moves FrameHostMsg_SetCookie to a Mojo message

content/common/render_frame_message_filter.mojom

Index: content/common/render_frame_message_filter.mojom
diff --git a/content/common/render_frame_message_filter.mojom b/content/common/render_frame_message_filter.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..909c4f379c7a818379e15da87219a9f6fc63acb6
--- /dev/null
+++ b/content/common/render_frame_message_filter.mojom
@@ -0,0 +1,14 @@
+// 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 content.mojom;
+
+import "url/mojo/url.mojom";
+
+interface RenderFrameMessageFilter {
+  // Sets a cookie. The cookie is set asynchronously, but will be available to
+  // any subsequent FrameHostMsg_GetCookies request.

[Tom Sepez, 2016/07/27 17:35:30]

Wouldn't we also have to move GetCookies to mojom as well to ensure we don't
race against the IPC impl?  Curious about how we ensure this.  Thanks.

+  SetCookie(int32 render_frame_id, url.mojom.Url url,
+      url.mojom.Url first_party_for_cookies, string cookie);
+};