From 3599adbcd3d39ae0ab0a8b4af78c68607b88442e Mon Sep 17 00:00:00 2001 From: RByers Date: Tue, 31 Dec 2013 11:11:47 -0500 Subject: [PATCH] Don't look for touch-action-delay support Chrome 33 has a bug where the CSS OM objects exist for touchActionDelay even though parsing will always fail for them, so we'd incorrectly believe support was present. Let's wait until there's actually a Chrome build to test before trying to enable a touch-action-delay fast-path. --- src/touch.js | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/src/touch.js b/src/touch.js index dae7fc46..1e4a0f49 100644 --- a/src/touch.js +++ b/src/touch.js @@ -15,8 +15,13 @@ var CLICK_COUNT_TIMEOUT = 200; var ATTRIB = 'touch-action'; var INSTALLER; - var HAS_TOUCH_ACTION_DELAY = (typeof document.head.style.touchActionDelay) === 'string'; - + // The presence of touch event handlers blocks scrolling, and so we must be careful to + // avoid adding handlers unnecessarily. Chrome plans to add a touch-action-delay property + // (crbug.com/329559) to address this, and once we have that we can opt-in to a simpler + // handler registration mechanism. Rather than try to predict how exactly to opt-in to + // that we'll just leave this disabled until there is a build of Chrome to test. + var HAS_TOUCH_ACTION_DELAY = false; + // handler block for native touch events var touchEvents = { scrollType: new WeakMap(),