Switching ExtensionSpecialStoragePolicy::IsStorageDurable to use DurableStoragePermissionContext.

chrome/browser/extensions/extension_special_storage_policy.h

Index: chrome/browser/extensions/extension_special_storage_policy.h
diff --git a/chrome/browser/extensions/extension_special_storage_policy.h b/chrome/browser/extensions/extension_special_storage_policy.h
index 31412c715993bedb4709985ed5e11616793c0333..f070dcc214111b4910fc34fd23023bf04201026e 100644
--- a/chrome/browser/extensions/extension_special_storage_policy.h
+++ b/chrome/browser/extensions/extension_special_storage_policy.h
@@ -31,7 +31,7 @@ class Extension;
 class ExtensionSpecialStoragePolicy : public storage::SpecialStoragePolicy {
  public:
   explicit ExtensionSpecialStoragePolicy(
-      content_settings::CookieSettings* cookie_settings);
+      content::BrowserContext* browser_context);

[pfeldman, 2016/09/23 17:12:20]

As a part of the chrome internal API, you should prefer using Profile over the
context.

 
   // storage::SpecialStoragePolicy methods used by storage subsystems and the
   // browsing data remover. These methods are safe to call on any thread.
@@ -94,7 +94,9 @@ class ExtensionSpecialStoragePolicy : public storage::SpecialStoragePolicy {
   SpecialCollection file_handler_extensions_;
   SpecialCollection isolated_extensions_;
   SpecialCollection content_capabilities_unlimited_extensions_;
+
   scoped_refptr<content_settings::CookieSettings> cookie_settings_;
+  content::BrowserContext* browser_context_; // weak reference.

[pfeldman, 2016/09/23 17:12:20]

It is either WeakPtr or a raw pointer. In this case it is raw, no need to say
weak - it is clear from the code that you use raw.

 };
 
 #endif  // CHROME_BROWSER_EXTENSIONS_EXTENSION_SPECIAL_STORAGE_POLICY_H_