Index: content/browser/renderer_host/input/input_router_impl.cc |
diff --git a/content/browser/renderer_host/input/input_router_impl.cc b/content/browser/renderer_host/input/input_router_impl.cc |
index 741d145d1eeb4a2c9d2c073f57deec4f5f4e4fc0..c73ccd33fb55b29ba05632407d6a45c101812404 100644 |
--- a/content/browser/renderer_host/input/input_router_impl.cc |
+++ b/content/browser/renderer_host/input/input_router_impl.cc |
@@ -217,6 +217,7 @@ void InputRouterImpl::SendGestureEvent( |
void InputRouterImpl::SendTouchEvent( |
const TouchEventWithLatencyInfo& touch_event) { |
+ LOG(ERROR) << "Queueing touch event"; |
touch_event_queue_->QueueEvent(touch_event); |
} |
@@ -244,6 +245,7 @@ void InputRouterImpl::SendMouseEventImmediately( |
void InputRouterImpl::SendTouchEventImmediately( |
const TouchEventWithLatencyInfo& touch_event) { |
+ LOG(ERROR) << "Skipping Queue"; |
FilterAndSendWebInputEvent(touch_event.event, touch_event.latency, false); |
} |
@@ -259,6 +261,8 @@ const NativeWebKeyboardEvent* InputRouterImpl::GetLastKeyboardEvent() const { |
} |
bool InputRouterImpl::ShouldForwardTouchEvent() const { |
+ if (!has_touch_handler_) |
+ LOG(ERROR) << "No touch handler"; |
// Always send a touch event if the renderer has a touch-event handler. It is |
// possible that a renderer stops listening to touch-events while there are |
// still events in the touch-queue. In such cases, the new events should still |
@@ -296,6 +300,7 @@ bool InputRouterImpl::OnMessageReceived(const IPC::Message& message) { |
void InputRouterImpl::OnTouchEventAck(const TouchEventWithLatencyInfo& event, |
InputEventAckState ack_result) { |
+ LOG(ERROR) << "Touch Event Ack"; |
ack_handler_->OnTouchEventAck(event, ack_result); |
} |