PlzNavigate: AppCache support.

content/common/navigation_params.h

Index: content/common/navigation_params.h
diff --git a/content/common/navigation_params.h b/content/common/navigation_params.h
index 98757a7303b941944faab686f576dac7240c021c..7fce0cc4794f0673bdbed27805d44299a7d6bfc5 100644
--- a/content/common/navigation_params.h
+++ b/content/common/navigation_params.h
@@ -325,6 +325,10 @@ struct CONTENT_EXPORT RequestNavigationParams {
   // it will always be equal to kInvalidServiceWorkerProviderId.
   int service_worker_provider_id;
 
+  // PlzNavigate
+  // The AppCache host id to be used to identify this navigation.
+  int appcache_host_id;

[clamy, 2016/11/25 13:32:24]

We've talked about introducing a navigation_id in the past (for example by
incrementing a global counter each time we create a NavigationRequest). I'm
wondering if we should do that and use it in lieu of having two different ids,
one for appcache and one for sw. I don't feel strongly on the question, though.

[ananta, 2016/11/28 21:36:53]

If it ok with you we can look into this for a subsequent patch. 

[clamy, 2016/11/30 17:40:22]

Acknowledged. As I mentioned, I don't feel strongly about it.

+
   // True if the navigation originated due to a user gesture.
   bool has_user_gesture;