Index: content/browser/renderer_host/render_widget_host.h |
diff --git a/content/browser/renderer_host/render_widget_host.h b/content/browser/renderer_host/render_widget_host.h |
index 49b7129bb52557c318efc86cf0283f07e378217c..70e67f242b597836f0ec85c5b3b929e8ea79dc1f 100644 |
--- a/content/browser/renderer_host/render_widget_host.h |
+++ b/content/browser/renderer_host/render_widget_host.h |
@@ -261,9 +261,7 @@ class RenderWidgetHost : public IPC::Channel::Listener, |
virtual void OnMouseActivate(); |
void ForwardWheelEvent(const WebKit::WebMouseWheelEvent& wheel_event); |
virtual void ForwardKeyboardEvent(const NativeWebKeyboardEvent& key_event); |
-#if defined(TOUCH_UI) |
virtual void ForwardTouchEvent(const WebKit::WebTouchEvent& touch_event); |
-#endif |
// Update the text direction of the focused input element and notify it to a |
@@ -590,6 +588,19 @@ class RenderWidgetHost : public IPC::Channel::Listener, |
// would be queued) results in very slow scrolling. |
WheelEventQueue coalesced_mouse_wheel_events_; |
+ // True if a touch move event was sent to the renderer view and we are waiting |
+ // for a corresponding ACK message. |
+ bool touch_move_pending_; |
+ |
+ // If a touch move event comes in while we are waiting for an ACK for a |
+ // previously sent touch move event, it will be stored here. A touch event |
+ // stores the location of the moved point, instead of the amount that it |
+ // moved. So it is not necessary to coalesce the move events (as is done for |
+ // mouse wheel events). Storing the most recent event for dispatch is |
+ // sufficient. |
+ WebKit::WebTouchEvent queued_touch_event_; |
+ bool touch_event_is_queued_; |
+ |
// The time when an input event was sent to the RenderWidget. |
base::TimeTicks input_event_start_time_; |