Remove the Extensions URLRequestContext

chrome/browser/extensions/data_deleter.cc

Index: chrome/browser/extensions/data_deleter.cc
diff --git a/chrome/browser/extensions/data_deleter.cc b/chrome/browser/extensions/data_deleter.cc
index 46518b0d0f4c446de1e6916ebc684f3d3ae8ae8d..d3488f566dcf83593af150a2b3729d1880812517 100644
--- a/chrome/browser/extensions/data_deleter.cc
+++ b/chrome/browser/extensions/data_deleter.cc
@@ -28,30 +28,9 @@ void DataDeleter::StartDeleting(Profile* profile,
 
   const GURL& site = Extension::GetBaseURLFromExtensionId(extension_id);
 
-  content::StoragePartition* partition =
-      BrowserContext::GetStoragePartitionForSite(profile, site);
-
-  if (storage_origin.SchemeIs(extensions::kExtensionScheme)) {
-    // TODO(ajwong): Cookies are not properly isolated for
-    // chrome-extension:// scheme.  (http://crbug.com/158386).
-    //
-    // However, no isolated apps actually can write to kExtensionScheme
-    // origins. Thus, it is benign to delete from the
-    // RequestContextForExtensions because there's nothing stored there. We
-    // preserve this code path without checking for isolation because it's
-    // simpler than special casing.  This code should go away once we merge
-    // the various URLRequestContexts (http://crbug.com/159193).
-    partition->AsyncClearDataForOrigin(
-        content::StoragePartition::kAllStorage,
-        storage_origin,
-        profile->GetRequestContextForExtensions());
-  } else {
-    // We don't need to worry about the media request context because that
-    // shares the same cookie store as the main request context.
-    partition->AsyncClearDataForOrigin(content::StoragePartition::kAllStorage,
-                                       storage_origin,
-                                       partition->GetURLRequestContext());
-  }
+  BrowserContext::GetStoragePartitionForSite(profile, site)->
+      AsyncClearDataForOrigin(content::StoragePartition::kAllStorage,
+                              storage_origin);
 
   // Begin removal of the settings for the current extension.
   profile->GetExtensionService()->settings_frontend()->