Make touch-based synthetic gesture take touch slop into account.

content/browser/renderer_host/input/synthetic_gesture_target_aura.cc

Index: content/browser/renderer_host/input/synthetic_gesture_target_aura.cc
diff --git a/content/browser/renderer_host/input/synthetic_gesture_target_aura.cc b/content/browser/renderer_host/input/synthetic_gesture_target_aura.cc
index 1d5c6a8d29c6e47aac67bae5999e81f0540222ab..b2f0e66bcafc6442f0bf455facd84ad141aef30e 100644
--- a/content/browser/renderer_host/input/synthetic_gesture_target_aura.cc
+++ b/content/browser/renderer_host/input/synthetic_gesture_target_aura.cc
@@ -11,6 +11,7 @@
 #include "ui/aura/client/screen_position_client.h"
 #include "ui/aura/root_window.h"
 #include "ui/aura/window.h"
+#include "ui/events/gestures/gesture_configuration.h"
 
 using blink::WebTouchEvent;
 using blink::WebMouseWheelEvent;
@@ -70,4 +71,8 @@ bool SyntheticGestureTargetAura::SupportsSyntheticGestureSourceType(
       gesture_source_type == SyntheticGestureParams::MOUSE_INPUT;
 }
 
+int SyntheticGestureTargetAura::GetTouchSlopInDips() const {
+  return ui::GestureConfiguration::max_touch_move_in_pixels_for_click();

[bulach, 2013/12/02 18:24:51]

is this "inclusive" ?
as in, is the test < or <=, and should this have + 1 if the latter?

[Dominik Grewe, 2013/12/02 18:50:04]

Good point. The test seems to be for < (although the name of the variable
suggests otherwise). But what we actually want is <=, i.e. the distance it can
move without being considered moving; that's what we get for Android (I'll
update the comment in synthetic_gesture_target.h. So it should be - 1 if I'm not
mistaken.

+}
+
 }  // namespace content