WebFonts: reset m_loadLimitState on memory cache revalidation

third_party/WebKit/Source/core/fetch/ResourceFetcher.cpp

Index: third_party/WebKit/Source/core/fetch/ResourceFetcher.cpp
diff --git a/third_party/WebKit/Source/core/fetch/ResourceFetcher.cpp b/third_party/WebKit/Source/core/fetch/ResourceFetcher.cpp
index 3948e207db0502630466315551d47a537432a672..f992ca5fd96a8f6d4943a06f71de69fb50b60c39 100644
--- a/third_party/WebKit/Source/core/fetch/ResourceFetcher.cpp
+++ b/third_party/WebKit/Source/core/fetch/ResourceFetcher.cpp
@@ -541,6 +541,9 @@ void ResourceFetcher::initializeRevalidation(const FetchRequest& request, Resour
     ASSERT(!resource->isCacheValidator());
     ASSERT(!context().isControlledByServiceWorker());
 
+    // Each resource may need a special initialization to load again.
+    resource->prepareToRevalidate();

[hiroshige, 2016/04/19 07:51:50]

How about calling prepareToRevalidate() in setRevalidatingRequest()?
By doing so, Resource::setRevalidatingRequest() will be the single point of
modification to Resource for revalidation start.

[Takashi Toyoshima, 2016/04/19 08:39:01]

Thanks, that sounds smart, and I can just make the method virtual to initialize
font specific field.

+
     ResourceRequest revalidatingRequest(resource->resourceRequest());
     revalidatingRequest.clearHTTPReferrer();
     initializeResourceRequest(revalidatingRequest, resource->getType(), request.defer());