Add chrome-native:// scheme.
The new scheme will be used to show pages rendered by the native
platform widgets (Android's view system in particular).
Decoupling the need for a renderer from WebContents was deemed to be
too drastic and risky, so we plan on using a new scheme that is
renderered as about:blank in the renderer and does not force a new
renderer to be created on the next navigation (see SetSite in
DidNavigate). This will allow us to use the same navigation handling/
site instance security already in place without a bunch of special
handling.
BUG=178915
Review URL: https://chromiumcodereview.appspot.com/15675024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207702 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/content/browser/web_contents/web_contents_impl.h b/content/browser/web_contents/web_contents_impl.h
index db1f4454..df7d5358 100644
--- a/content/browser/web_contents/web_contents_impl.h
+++ b/content/browser/web_contents/web_contents_impl.h
@@ -640,6 +640,10 @@
const LoadCommittedDetails& details,
const ViewHostMsg_FrameNavigate_Params& params);
+ // Specifies whether the passed in URL should be assigned as the site of the
+ // current SiteInstance, if it does not yet have a site.
+ bool ShouldAssignSiteForURL(const GURL& url);
+
// If our controller was restored, update the max page ID associated with the
// given RenderViewHost to be larger than the number of restored entries.
// This is called in CreateRenderView before any navigations in the RenderView
