InputHandlerProxy to inform blink scheduler of input events

content/renderer/input/input_handler_wrapper.cc

Index: content/renderer/input/input_handler_wrapper.cc
diff --git a/content/renderer/input/input_handler_wrapper.cc b/content/renderer/input/input_handler_wrapper.cc
index 6ff0033939a3875b8090ba8afb03493c31288baa..1e74375d3dc872226e59356b59eed8ad9a018fcb 100644
--- a/content/renderer/input/input_handler_wrapper.cc
+++ b/content/renderer/input/input_handler_wrapper.cc
@@ -21,6 +21,7 @@ InputHandlerWrapper::InputHandlerWrapper(
       routing_id_(routing_id),
       input_handler_proxy_(input_handler.get(), this),
       main_loop_(main_loop),
+      web_scheduler_proxy_(blink::WebSchedulerProxy::create()),
       render_view_impl_(render_view_impl) {
   DCHECK(input_handler);
 }
@@ -57,4 +58,8 @@ void InputHandlerWrapper::DidStopFlinging() {
   input_handler_manager_->DidStopFlinging(routing_id_);
 }
 
+void InputHandlerWrapper::DidHandleInputEvent() {
+  web_scheduler_proxy_.didReceiveInputEvent();

[jdduke (slow), 2014/09/10 17:02:26]

What kind of work might this call trigger?

[Sami, 2014/09/10 17:23:00]

It lets the scheduler know the time of the last incoming input event so we can
estimate if they user is interacting with the device or not. This notification
by itself won't cause any work other than grabbing a lock (or an atomic write),
looking at the current time and setting a flag.

+}
+
 }  // namespace content