Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
tap double trigger on chrome 55 #1249
Confirming what @Xaber20110202 reported. Since Chrome 55 for mobile is out, the tap event (coming with the touch module) is misbehaving - once it will trigger twice on single tap, other times it may not trigger at all, requiring 2nd tap for something to happen.
The reason behind this behaviour is PointerEvents added in Chrome since version 55. More info about these and why were added:
All this means that since Chrome 55 apart from any touch event being fired (e.g. "touchstart"), Chrome will also fire the respective pointer one (e.g. "pointerdown" is fired together with "touchstart"). Zepto already has some pointer events handling added for MS Edge and IE11, which seems to be incompatible with Chrome's pointer events fired together with touch events.
To get the touch module fixed it will have to either be rewritten so to handle separately/properly pointer events fired by Chrome and MS browsers or, as a quick hack, ignore pointer events if fired and the browser is Chrome. Another solution is what @Xaber20110202 mentioned as well - to simply remove all pointer events handling from the touch module, which works very well given one doesn't have to support MS mobile browsers. This is also the quick solution I went for couple of weeks ago when stumbled upon this issue...