Refactor the forPreload flag to mean speculative preload.

third_party/WebKit/Source/core/loader/LinkLoader.cpp

Index: third_party/WebKit/Source/core/loader/LinkLoader.cpp
diff --git a/third_party/WebKit/Source/core/loader/LinkLoader.cpp b/third_party/WebKit/Source/core/loader/LinkLoader.cpp
index 599b82c937d68967cc23ab6dd94fc86c16d8e32a..4110e69c89f8d0dbb739cc4c7c81b084a958ad31 100644
--- a/third_party/WebKit/Source/core/loader/LinkLoader.cpp
+++ b/third_party/WebKit/Source/core/loader/LinkLoader.cpp
@@ -339,7 +339,6 @@ static Resource* preloadIfNeeded(const LinkRelAttribute& relAttribute,
         OtherMessageSource, VerboseMessageLevel,
         String("Preload triggered for " + href.host() + href.path())));
   }
-  linkRequest.setForPreload(true, monotonicallyIncreasingTime());

[Charlie Harrison, 2017/02/05 18:39:11]

I think this will affect metrics, but I think it is correct and those metrics
should only be for speculative preloads.

[Yoav Weiss, 2017/02/06 09:58:35]

Yeah, I agree

   linkRequest.setLinkPreload(true);
   return document.loader()->startPreload(resourceType.value(), linkRequest);
 }