Hook up DidReceiveInputEvent to the blink scheduler

content/renderer/input/input_handler_proxy.cc

Index: content/renderer/input/input_handler_proxy.cc
diff --git a/content/renderer/input/input_handler_proxy.cc b/content/renderer/input/input_handler_proxy.cc
index d9a34ada63b15efc548b0188ee606161997a3bfb..ccc9c9f392e6d7ec6d32c972c864e6a303350687 100644
--- a/content/renderer/input/input_handler_proxy.cc
+++ b/content/renderer/input/input_handler_proxy.cc
@@ -619,6 +619,7 @@ void InputHandlerProxy::Animate(base::TimeTicks time) {
                                   kMaxSecondsFromFlingTimestampToFirstAnimate) {
       fling_parameters_.startTime = monotonic_time_sec;
       input_handler_->SetNeedsAnimate();
+      client_->DidReceiveInputEvent();

[Sami, 2014/11/03 23:54:07]

It feels a little wrong to lie to the client about getting input events. How
about we add a new notification called DidAnimateFling, or just DidAnimate?

[alex clarke (OOO till 29th), 2014/11/04 01:14:35]

Done.

       return;
     }
   }
@@ -632,6 +633,7 @@ void InputHandlerProxy::Animate(base::TimeTicks time) {
 
   if (fling_is_active) {
     input_handler_->SetNeedsAnimate();
+    client_->DidReceiveInputEvent();
   } else {
     TRACE_EVENT_INSTANT0("input",
                          "InputHandlerProxy::animate::flingOver",