Added TapSuppressionController params to gesture configurations

chrome/browser/resources/gesture_config.js

Index: chrome/browser/resources/gesture_config.js
diff --git a/chrome/browser/resources/gesture_config.js b/chrome/browser/resources/gesture_config.js
index 74607f9ec7144eddad493a9d6379609bf4b9a706..16c60b38d6027a73ff8fca8a225a7065b1d9b2ab 100644
--- a/chrome/browser/resources/gesture_config.js
+++ b/chrome/browser/resources/gesture_config.js
@@ -132,6 +132,16 @@ function GestureConfig() {
   /** List of fields used to dynamically build form. **/
   var GESTURE_FIELDS = [
     {
+      key: 'fling_max_cancel_to_down_time_in_ms',

[rjkroege, 2013/01/03 22:42:49]

all the remaining params are in seconds yes? shouldn't this one be too?

[mohsen, 2013/01/04 16:14:22]

Yes, I had noticed that point. I used ms to keep the values as integers and
avoid double/int conversions. Also, I thought that the values will almost always
be small fractions of seconds, e.g. for tests we may set them to values like
.005 or 0.01 seconds which does not seem nice to me! But, I agree that having
them in seconds is more consistent with the rest of the params. What's your
opinion?

+      label: 'Maximum Cancel to Down Time for Tap Suppression',
+      units: 'milliseconds',
+    },
+    {
+      key: 'fling_max_tap_gap_time_in_ms',
+      label: 'Maximum Tap Gap Time for Tap Suppression',
+      units: 'milliseconds',
+    },
+    {
       key: 'long_press_time_in_seconds',
       label: 'Long Press Time',
       units: 'seconds'