Enforce referrer policies for workers

Source/core/dom/Document.cpp

Index: Source/core/dom/Document.cpp
diff --git a/Source/core/dom/Document.cpp b/Source/core/dom/Document.cpp
index a1c645fb4b0399c60eaeb0e5e602987fa003714d..9c0b558fc0a87bba6eceaf098bc41000a66e1032 100644
--- a/Source/core/dom/Document.cpp
+++ b/Source/core/dom/Document.cpp
@@ -465,7 +465,6 @@ Document::Document(const DocumentInit& initializer, DocumentClassFlags documentC
     , m_loadEventDelayCount(0)
     , m_loadEventDelayTimer(this, &Document::loadEventDelayTimerFired)
     , m_pluginLoadingTimer(this, &Document::pluginLoadingTimerFired)
-    , m_referrerPolicy(ReferrerPolicyDefault)
     , m_writeRecursionIsTooDeep(false)
     , m_writeRecursionDepth(0)
     , m_taskRunner(MainThreadTaskRunner::create(this))
@@ -3065,16 +3064,6 @@ void Document::processReferrerPolicy(const String& policy)
         addConsoleMessage(ConsoleMessage::create(RenderingMessageSource, ErrorMessageLevel, "Failed to set referrer policy: The value '" + policy + "' is not one of 'always', 'default', 'never', 'no-referrer', 'no-referrer-when-downgrade', 'origin', 'origin-when-crossorigin', or 'unsafe-url'. This document's referrer policy has been left unchanged."));
 }
 
-void Document::setReferrerPolicy(ReferrerPolicy referrerPolicy)
-{
-    // FIXME: Can we adopt the CSP referrer policy merge algorithm? Or does the web rely on being able to modify the referrer policy in-flight?
-    UseCounter::count(this, UseCounter::SetReferrerPolicy);
-    if (m_referrerPolicy != ReferrerPolicyDefault)
-        UseCounter::count(this, UseCounter::ResetReferrerPolicy);
-
-    m_referrerPolicy = referrerPolicy;
-}
-
 String Document::outgoingReferrer()
 {
     // See http://www.whatwg.org/specs/web-apps/current-work/#fetching-resources