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

Unified Diff: chrome/browser/ui/browser_navigator_params.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: chrome/browser/ui/browser_navigator_params.h
diff --git a/chrome/browser/ui/browser_navigator_params.h b/chrome/browser/ui/browser_navigator_params.h
index bf40e6781e709db6d8311cab5e6e07366d3a143d..77c03c1285a594269660ded957e6ed9a39973027 100644
--- a/chrome/browser/ui/browser_navigator_params.h
+++ b/chrome/browser/ui/browser_navigator_params.h
@@ -132,6 +132,12 @@ struct NavigateParams {
// |tabstrip_add_types|.
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;
sky 2017/04/20 21:00:57 I find the use of renderer mildly confusing here.
Łukasz Anforowicz 2017/04/20 21:56:05 Done.
+
// Sets browser->is_trusted_source. Default is false.
bool trusted_source;

Powered by Google App Engine
This is Rietveld 408576698