PlzNavigate: stop navigations when opening a document for write

content/browser/frame_host/frame_tree_node.cc

Index: content/browser/frame_host/frame_tree_node.cc
diff --git a/content/browser/frame_host/frame_tree_node.cc b/content/browser/frame_host/frame_tree_node.cc
index 655c46092ccd43acb579fd8813a123639ebb8f1f..bdc5b8cb7ab947b388399559809bc544f94f4cdb 100644
--- a/content/browser/frame_host/frame_tree_node.cc
+++ b/content/browser/frame_host/frame_tree_node.cc
@@ -426,7 +426,7 @@ void FrameTreeNode::ResetNavigationRequest(bool keep_state) {
   // informed that the navigation stopped.
   if (was_renderer_initiated) {
     current_frame_host()->Send(
-        new FrameMsg_Stop(current_frame_host()->GetRoutingID()));
+        new FrameMsg_DroppedNavigation(current_frame_host()->GetRoutingID()));

[nasko, 2017/03/09 05:19:28]

Hmm, why use the new IPC here? The navigation could have been reset for other
reasons than the one this CL is trying to fix.

[clamy, 2017/03/13 13:55:57]

Yes. But I don't think that the cancellation of one renderer-initiation on the
browser side should lead to all loads stopping in the renderer. In particular we
should not stop an ongoing load, but just inform the renderer that it should not
expect the navigation it sent to the browser to continue. This is what the new
FrameMsg_DroppedNavigation is meant to do (I mean to introduce this IPC as
something more general than this particular issue).

   }
 
 }