Make ResourceLoadPriority calculation simpler

third_party/WebKit/Source/core/html/LinkResource.cpp

Index: third_party/WebKit/Source/core/html/LinkResource.cpp
diff --git a/third_party/WebKit/Source/core/html/LinkResource.cpp b/third_party/WebKit/Source/core/html/LinkResource.cpp
index b213219abfb1535ce8569ece12cc4367e7fee31a..bee7573dd948efb51cd85a39e3a30d51ab84c257 100644
--- a/third_party/WebKit/Source/core/html/LinkResource.cpp
+++ b/third_party/WebKit/Source/core/html/LinkResource.cpp
@@ -77,8 +77,10 @@ LinkRequestBuilder::LinkRequestBuilder(HTMLLinkElement* owner)
 
 FetchRequest LinkRequestBuilder::build(bool lowPriority) const
 {
-    ResourceLoadPriority priority = lowPriority ? ResourceLoadPriorityVeryLow : ResourceLoadPriorityUnresolved;
-    return FetchRequest(ResourceRequest(m_owner->document().completeURL(m_url)), m_owner->localName(), m_charset, priority);
+    FetchRequest request(ResourceRequest(m_owner->document().completeURL(m_url)), m_owner->localName(), m_charset);
+    if (lowPriority)
+        request.setDefer(FetchRequest::LazyLoad);

[Yoav Weiss, 2016/06/25 08:37:59]

AFAICT, this mainly impacts non-matching styles & alternate links, marking them
as lazy, which will effectively result in them being of very low priority (and
therefore no functional change here). Is that a correct analysis?  

[Nate Chapin, 2016/06/27 19:46:16]

Yes, that's my understanding.

+    return request;
 }
 
 } // namespace blink