New WebContents created via ctrl-click should be in a new process.

content/public/browser/page_navigator.h

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..3a46e0db3f9ba9fe63f565c2c86ed22b1a2fe2f5 100644
--- a/content/public/browser/page_navigator.h
+++ b/content/public/browser/page_navigator.h
@@ -82,6 +82,14 @@ struct CONTENT_EXPORT OpenURLParams {
   // The disposition requested by the navigation source.
   WindowOpenDisposition disposition;
 
+  // Controls whether newly created web contents (in case |disposition| asks for
+  // a new tab or window) should attempt to reuse the renderer process of
+  // |source_site_instance|.  For example - new contents created after
+  // ctrl-clicking a link should use always a new renderer, but
+  // chrome.windows.create extensions API should try to keep the new contents in
+  // the same extension process (if same-site).
+  bool use_new_renderer_for_new_contents;
+
   // The transition type of navigation.
   ui::PageTransition transition;