Remove ExtensionProcessManager and move its functionality onto

ExtensionsService.

Also add "chrome-extension" to the list of schemes that BrowsingInstance
groups per-site, instead of per-tab.  This means that navigating to an
extension URL will use the same process as a running extension toolstrip.
Review URL: http://codereview.chromium.org/77002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13887 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 3 insertions, 5 deletions

diff --git a/chrome/browser/extensions/extension_view_unittest.cc b/chrome/browser/extensions/extension_view_unittest.cc
index 360df57..e493421 100755
--- a/chrome/browser/extensions/extension_view_unittest.cc
+++ b/chrome/browser/extensions/extension_view_unittest.cc
@@ -6,7 +6,6 @@
 #include "chrome/browser/browser.h"
 #include "chrome/browser/renderer_host/render_view_host.h"
 #include "chrome/browser/extensions/extension_error_reporter.h"
-#include "chrome/browser/extensions/extension_process_manager.h"
 #include "chrome/browser/extensions/extension_view.h"
 #include "chrome/browser/extensions/extensions_service.h"
 #include "chrome/browser/extensions/test_extension_loader.h"
@@ -95,9 +94,8 @@ IN_PROC_BROWSER_TEST_F(ExtensionViewTest, Index) {
   GURL url = Extension::GetResourceURL(extension->url(), "toolstrip1.html");
 
   // Start the extension process and wait for it to show a javascript alert.
-  MockExtensionView view(
-      extension, url, ExtensionProcessManager::GetInstance()->
-          GetSiteInstanceForURL(url, browser()->profile()),
-          NULL);  // TODO(erikkay): do we need to get a Browser here?
+  MockExtensionView view(extension, url,
+      browser()->profile()->GetExtensionsService()->GetSiteInstanceForURL(url),
+      browser());
   EXPECT_TRUE(view.got_message());
 }