Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1633)

Unified Diff: content/public/browser/page_navigator.h

Issue 2686943002: New WebContents created via ctrl-click should be in a new process. (Closed)
Patch Set: s/use_new_renderer.../force_new_renderer.../ + comment changes. Created 3 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: content/public/browser/page_navigator.h
diff --git a/content/public/browser/page_navigator.h b/content/public/browser/page_navigator.h
index eb9e6a83e15df25bca29789867a3d613a0b88504..071639ec5966c21d41de73e792176eaf9e597b34 100644
--- a/content/public/browser/page_navigator.h
+++ b/content/public/browser/page_navigator.h
@@ -82,6 +82,12 @@ struct CONTENT_EXPORT OpenURLParams {
// The disposition requested by the navigation source.
WindowOpenDisposition disposition;
+ // Controls creation of new web contents (in case |disposition| asks for a new
+ // tab or window). If |force_new_renderer_for_new_contents| is true, then we
+ // try to put the new contents in a new renderer, even if they are same-site
+ // as |source_site_instance| (this is subject to renderer process limits).
+ bool force_new_renderer_for_new_contents;
+
// The transition type of navigation.
ui::PageTransition transition;

Powered by Google App Engine
This is Rietveld 408576698