From 7a2155319cc56f1decfca530f614634c8b741256 Mon Sep 17 00:00:00 2001 From: Matt Brubeck Date: Wed, 8 Sep 2010 13:26:47 -0700 Subject: [PATCH] Revert some incorrect changes from bug 593499 [r=stechz] --HG-- extra : rebase_source : 3ef0a007d75354c2e2cd9ba26de217d7a9a36bd9 --- mobile/chrome/content/InputHandler.js | 7 ++++--- mobile/chrome/content/content.js | 2 +- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/mobile/chrome/content/InputHandler.js b/mobile/chrome/content/InputHandler.js index eb1fc5de846d..2c460b956923 100644 --- a/mobile/chrome/content/InputHandler.js +++ b/mobile/chrome/content/InputHandler.js @@ -42,11 +42,12 @@ * * ***** END LICENSE BLOCK ***** */ -// how many msecs elapse before two taps are not a double tap +// Maximum delay in ms between the two taps of a double-tap const kDoubleClickInterval = 400; -// threshold in ms to detect if the click is possibly a dblClick -const kDoubleClickThreshold = 300; +// If a tap lasts longer than this duration in ms, treat it as a single-tap +// immediately instead of waiting for a possible double tap. +const kDoubleClickThreshold = 200; // threshold in pixels for sensing a tap as opposed to a pan const kTapRadius = 25; diff --git a/mobile/chrome/content/content.js b/mobile/chrome/content/content.js index 0520ac7c9390..aabbc3b0d1e4 100644 --- a/mobile/chrome/content/content.js +++ b/mobile/chrome/content/content.js @@ -2,7 +2,7 @@ dump("###################################### content loaded\n"); // how many milliseconds before the mousedown and the overlay of an element -const kTapOverlayTimeout = 300; +const kTapOverlayTimeout = 200; let Cc = Components.classes; let Ci = Components.interfaces;