PlzNavigate: set browser_initiated based on the NavigationEntry

content/browser/frame_host/navigation_request.h

Index: content/browser/frame_host/navigation_request.h
diff --git a/content/browser/frame_host/navigation_request.h b/content/browser/frame_host/navigation_request.h
index 4dca8882a7390b1b3eda190bc14b10b3b42409e0..d5c7f080d44737751fcd98fe12806c5697fb53e0 100644
--- a/content/browser/frame_host/navigation_request.h
+++ b/content/browser/frame_host/navigation_request.h
@@ -130,6 +130,8 @@ class CONTENT_EXPORT NavigationRequest : public NavigationURLLoaderDelegate {
 
   bool browser_initiated() const { return browser_initiated_ ; }
 
+  bool may_transfer() const { return may_transfer_; }

[nasko, 2016/12/22 17:33:45]

nit: Using "can" vs "may" seems a bit more appropriate here. We want to check
whether this request is allowed to transfer (aka "can") not whether it might
possibly transfer (aka "may").

[clamy, 2016/12/22 17:37:40]

I was worried that it might get confusing since its possible that may_transfer
is false, but we will still end up transferring it (old transfer navigation
case).

+
   void SetWaitingForRendererResponse() {
     DCHECK(state_ == NOT_STARTED);
     state_ = WAITING_FOR_RENDERER_RESPONSE;
@@ -169,6 +171,7 @@ class CONTENT_EXPORT NavigationRequest : public NavigationURLLoaderDelegate {
                     const BeginNavigationParams& begin_params,
                     const RequestNavigationParams& request_params,
                     bool browser_initiated,
+                    bool may_transfer,
                     const FrameNavigationEntry* frame_navigation_entry,
                     const NavigationEntryImpl* navitation_entry);
 
@@ -229,6 +232,15 @@ class CONTENT_EXPORT NavigationRequest : public NavigationURLLoaderDelegate {
   // The type of SiteInstance associated with this navigation.
   AssociatedSiteInstanceType associated_site_instance_type_;
 
+  // Whether the request may be transferred to a different process upon commit.
+  // True for browser-initiated navigations and renderer-inititated navigations
+  // started via the OpenURL path.
+  // Note: the RenderFrameHostManager may still decide to have the navigation
+  // commit in a different renderer process if it detects that a renderer
+  // transfer is needed. This is the case in particular when --site-per-process
+  // is enabled.
+  bool may_transfer_;
+
   std::unique_ptr<NavigationHandleImpl> navigation_handle_;
 
   // Holds the ResourceResponse and the StreamHandle for the navigation while