PlzNavigate: Make ServiceWorker work with PlzNavigate.

content/browser/service_worker/service_worker_request_handler.h

Index: content/browser/service_worker/service_worker_request_handler.h
diff --git a/content/browser/service_worker/service_worker_request_handler.h b/content/browser/service_worker/service_worker_request_handler.h
index 2c14eb1b862676854d13107880525399a5fdb004..7ea939cc759e07b861dd57efd2506d73ad43c2c7 100644
--- a/content/browser/service_worker/service_worker_request_handler.h
+++ b/content/browser/service_worker/service_worker_request_handler.h
@@ -31,6 +31,7 @@ namespace content {
 
 class ResourceContext;
 class ResourceRequestBody;
+class NavigationURLLoaderImplCore;
 class ServiceWorkerContextCore;
 class ServiceWorkerContextWrapper;
 class ServiceWorkerProviderHost;
@@ -60,7 +61,8 @@ class CONTENT_EXPORT ServiceWorkerRequestHandler
       ResourceType resource_type,
       RequestContextType request_context_type,
       RequestContextFrameType frame_type,
-      scoped_refptr<ResourceRequestBody> body);
+      scoped_refptr<ResourceRequestBody> body,
+      NavigationURLLoaderImplCore* loader);

[clamy, 2015/08/27 11:53:45]

I'm a bit concerned about providing a raw pointer to the
NavigationURLLoaderImplCore, since the URLRequest will outlive it (it gets
destroyed when the request is ready to commit). I think transitioning to a weak
pointer would avoid possible edge cases here.

[Fabrice (no longer in Chrome), 2015/08/28 15:40:16]

The loader is only used in this fashion in this method:
loader->SetServiceWorkerProviderHost(scoped_provider_host.Pass());
I don't think there is a risk of "losing" the pointer in the meantime. Or I am
misunderstanding your point.

 
   // Returns the handler attached to |request|. This may return NULL
   // if no handler is attached.