Support ReferrerPolicy in Fetch API

third_party/WebKit/Source/modules/fetch/Request.idl

Index: third_party/WebKit/Source/modules/fetch/Request.idl
diff --git a/third_party/WebKit/Source/modules/fetch/Request.idl b/third_party/WebKit/Source/modules/fetch/Request.idl
index faa25cbc14b934891d94f888efe90282e3279245..224fdcf9d1cc15b6b404026a624931c0690814ea 100644
--- a/third_party/WebKit/Source/modules/fetch/Request.idl
+++ b/third_party/WebKit/Source/modules/fetch/Request.idl
@@ -16,6 +16,14 @@ enum RequestContext {
 enum RequestMode { "navigate", "same-origin", "no-cors", "cors" };
 enum RequestCredentials { "omit", "same-origin", "include" };
 enum RequestRedirect { "follow", "error", "manual" };
+enum ReferrerPolicy {
+    "",
+    "no-referrer",
+    "no-referrer-when-downgrade",
+    "origin-only",
+    "origin-when-cross-origin",
+    "unsafe-url"

[estark, 2016/04/18 09:21:27]

Does this need to include the newly added
"no-referrer-when-downgrade-origin-when-cross-origin" value? Or does it only
need to include official spec'ed non-experimental values?

[yhirano, 2016/04/19 14:24:09]

I'd like to not include no-referrer-when-downgrade-origin-when-cross-origin.

+};
 
 [
     Constructor(RequestInfo input, optional Dictionary requestInitDict),
@@ -28,6 +36,7 @@ enum RequestRedirect { "follow", "error", "manual" };
     readonly attribute USVString url;
     [ImplementedAs=getHeaders] readonly attribute Headers headers;
     readonly attribute DOMString referrer;
+    readonly attribute ReferrerPolicy referrerPolicy;
     readonly attribute RequestMode mode;
     readonly attribute RequestCredentials credentials;
     readonly attribute RequestRedirect redirect;