Modify --isolate-extensions to not isolate hosted apps.

content/common/site_isolation_policy.h

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CONTENT_COMMON_SITE_ISOLATION_POLICY_H_
 #define CONTENT_COMMON_SITE_ISOLATION_POLICY_H_
 
 #include "base/basictypes.h"
 #include "content/common/content_export.h"
 #include "url/gurl.h"
@@ skipping 16 matching lines @@
   //
   // Note: Since cross-process frames will soon be possible by default, usage
   // should be limited to temporary stop-gaps.
   //
   // Instead of calling this method, prefer to examine object state to see
   // whether a particular frame happens to have a cross-process relationship
   // with another, or to consult DoesSiteRequireDedicatedProcess() to see if a
   // particular site merits protection.
   static bool AreCrossProcessFramesPossible();
 
-  // Returns true if pages loaded from |effective_url| ought to be handled only
-  // by a renderer process isolated from other sites. If --site-per-process is
-  // on the command line, this is true for all sites. In other site isolation
-  // modes, only a subset of sites will require dedicated processes.
-  //
-  // |effective_url| must be an effective URL -- practically speaking, that
-  // means that this function should only be called on the UI thread in the
-  // browser process.
-  static bool DoesSiteRequireDedicatedProcess(const GURL& effective_url);
+  // Returns true if every site should be placed in a dedicated process.
+  static bool UseDedicatedProcessesForAllSites();
 
   // Returns true if navigation and history code should maintain per-frame
   // navigation entries. This is an in-progress feature related to site
   // isolation, so the return value is currently tied to --site-per-process.
   // TODO(creis, avi): Make this the default, and eliminate this.
   static bool UseSubframeNavigationEntries();
 
   // Returns true if we are currently in a mode where the swapped out state
   // should not be used. Currently (as an implementation strategy) swapped out
   // is forbidden under --site-per-process, but our goal is to eliminate the
   // mode entirely. In code that deals with the swapped out state, prefer calls
   // to this function over consulting the switches directly. It will be easier
   // to grep, and easier to rip out.
   //
   // TODO(nasko): When swappedout:// is eliminated entirely, this function
   // should be removed and its callers cleaned up.
   static bool IsSwappedOutStateForbidden();
 
-  // Overrides the default site isolation mode so that all sites are
-  // isolated. Returns true if successful. Can fail if SiteIsolationPolicy
-  // has already been consulted at runtime prior to the override call --
-  // if so, try calling this earlier in the test, maybe before creating
-  // any renderer processes.
-  static bool IsolateAllSitesForTesting();
-
  private:
   SiteIsolationPolicy();  // Not instantiable.
 
   DISALLOW_COPY_AND_ASSIGN(SiteIsolationPolicy);
 };
 
 }  // namespace content
 
 #endif  // CONTENT_COMMON_SITE_ISOLATION_POLICY_H_