Don't consume user gesture in RenderFrameProxy::navigate.

content/renderer/render_frame_proxy.cc

Index: content/renderer/render_frame_proxy.cc
diff --git a/content/renderer/render_frame_proxy.cc b/content/renderer/render_frame_proxy.cc
index 8f429c68c4b94f2e76c960d3842550098535b48f..58adfeaa1590d963311f6742f93005356bc9e77a 100644
--- a/content/renderer/render_frame_proxy.cc
+++ b/content/renderer/render_frame_proxy.cc
@@ -460,9 +460,7 @@ void RenderFrameProxy::navigate(const blink::WebURLRequest& request,
       request.referrerPolicy());
   params.disposition = WindowOpenDisposition::CURRENT_TAB;
   params.should_replace_current_entry = should_replace_current_entry;
-  params.user_gesture =
-      blink::WebUserGestureIndicator::isProcessingUserGesture();
-  blink::WebUserGestureIndicator::consumeUserGesture();
+  params.user_gesture = request.hasUserGesture();

[alexmos, 2016/12/06 01:58:05]

We already set this on the request in RemoteFrame::navigate(request), so I'm
just reusing that here instead of re-computing.  (We end up never using this bit
on the browser side currently, fwiw.)  I noticed there's some other potential
user gesture cleanup in RemoteFrame::navigate (e.g., looks like
userGestureStatus is never actually used), but I'll try that out in another CL.

   Send(new FrameHostMsg_OpenURL(routing_id_, params));
 }