OOPIF: Data URLs are now rendered in the renderer that initiated the navigation.

chrome/browser/ui/browser_navigator.h

Index: chrome/browser/ui/browser_navigator.h
diff --git a/chrome/browser/ui/browser_navigator.h b/chrome/browser/ui/browser_navigator.h
index 4209927811452747814160386e8e2e8d14e6af60..8e787165ac1a9b181bf0b762d14b60be3b15c1ff 100644
--- a/chrome/browser/ui/browser_navigator.h
+++ b/chrome/browser/ui/browser_navigator.h
@@ -13,6 +13,7 @@
 #include "content/public/browser/browser_context.h"
 #include "content/public/browser/global_request_id.h"
 #include "content/public/browser/page_navigator.h"
+#include "content/public/browser/site_instance.h"
 #include "content/public/common/referrer.h"
 #include "ui/base/page_transition_types.h"
 #include "ui/base/window_open_disposition.h"
@@ -65,6 +66,10 @@ struct NavigateParams {
   GURL url;
   content::Referrer referrer;
 
+  // Site instance that initiated the navigation. Should only be used when a
+  // cross-site navigation is initiated by a remote frame.

[Charlie Reis, 2014/12/06 00:18:50]

Why?  It may only matter in that case for now, but it would be more consistent
to set it in all cases.

I'd suggest simplifying the comment to "SiteInstance of the frame that initiated
the navigation" and setting it in the LocalFrame case as well.

[lfg, 2014/12/08 20:45:32]

Done.

+  scoped_refptr<content::SiteInstance> source_site_instance;
+
   // The browser-global ID of the frame to navigate, or -1 for the main frame.
   int64 frame_tree_node_id;