PlzNavigate: don't stop all loaders when renderer-initiated nav fails

content/renderer/render_frame_impl.cc

Index: content/renderer/render_frame_impl.cc
diff --git a/content/renderer/render_frame_impl.cc b/content/renderer/render_frame_impl.cc
index bee34de98c77796c764103e60f9a6d25e58f8659..5ad73766a509d614cb0bb6cf0b1a67be979cdfce 100644
--- a/content/renderer/render_frame_impl.cc
+++ b/content/renderer/render_frame_impl.cc
@@ -1589,6 +1589,7 @@ bool RenderFrameImpl::OnMessageReceived(const IPC::Message& msg) {
     IPC_MESSAGE_HANDLER(FrameMsg_FailedNavigation, OnFailedNavigation)
     IPC_MESSAGE_HANDLER(FrameMsg_ReportContentSecurityPolicyViolation,
                         OnReportContentSecurityPolicyViolation)
+    IPC_MESSAGE_HANDLER(FrameMsg_DroppedNavigation, OnDroppedNavigation)
     IPC_MESSAGE_HANDLER(FrameMsg_GetSavableResourceLinks,
                         OnGetSavableResourceLinks)
     IPC_MESSAGE_HANDLER(FrameMsg_GetSerializedHtmlWithLocalLinks,
@@ -5312,6 +5313,11 @@ void RenderFrameImpl::OnReportContentSecurityPolicyViolation(
       BuildWebContentSecurityPolicyViolation(violation_params));
 }
 
+void RenderFrameImpl::OnDroppedNavigation() {

[Charlie Reis, 2017/03/23 16:52:53]

Maybe we should put this alongside OnStop() to make it clear that they're
related?

Looking at that one, I'm also wondering if we should notify observers in this
case.  Do you know if the two current listeners to RFO::OnStop would want to
hear this as well?

(Also, feel free to include a TODO to address the race.  I'm glad we're landing
this first, but we should acknowledge that it's worth coming back to.)

+  browser_side_navigation_pending_ = false;
+  frame_->clientDroppedNavigation();
+}
+
 WebNavigationPolicy RenderFrameImpl::decidePolicyForNavigation(
     const NavigationPolicyInfo& info) {
   // A content initiated navigation may have originated from a link-click,