Attempting to use $.Fastclick to improve the clickspeed on existing links on a HTC desire android 2.2 with the stock browser

$('a, button').fastClick(function() { alert('clicked!'); });

http://couch.arandomurl.com/couchtasks/_design/couchtasks/fastclick.html

E/browser ( 936): Console: Uncaught TypeError: Cannot read property '0' of undefined http://couch.arandomurl.com/couchtasks/_design/couchtasks/js/jQuery.fastClick.js:57

switching to event.originalEvent.touches gives

E/browser ( 936): Console: Uncaught TypeError: Cannot read property 'clientX' of undefined http://couch.arandomurl.com/couchtasks/_design/couchtasks/js/jQuery.fastClick.js:58

tested with jquery-git and jquery-1.5.2

I somehow managed to make your plugin work with xui.js for the time being, and it definitely makes a web app more responsive then the click events.

Everything seems to work great (week or so now) until you "double tap" something. Then all hell breaks loose. Granted, I think very few mobile users are 'double tapping' stuff to navigate around, but even an accidental double-tap can cause the links to break.

I'm not even sure if "double tap" events exist in Webkit, so I'm not really sure what is causing the problem. Would setting the timeout on "preventghostClick" to a lower interval help?

$(".button").fastClick(function() { console.debug(this.toString()); }

outputs [object Window], when it should output [object HtmlDivElement] (or whatever the button class is defined in). Any help would be appreciated.

Thanks.

hi there

this is just a small change to get the existing onclick handlers handled by fastclick automatically, as somebody requested in issue #13. it still degrades to "normal/manual" mode gracefully.

thanks

btw. this is my first pull-request ever... please support me with some feedback if i'm doing anything the wrong way :)

Replace

document.addEventListener('click', $.clickbuster.onClick, true);

with

    if (document.addEventListener){
      document.addEventListener('click', $.clickbuster.onClick, true); 
    } else if (document.attachEvent){
      document.attachEvent('onclick', $.clickbuster.onClick);
    }

I used a incorrect jQuery selector last time which meant that touchmove events weren't caught and incorrectly triggered a click. This pull request fixes that.

Hi, I've used this 'plugin' to change my chain of events from the browser version of my website. When I test the website using chrome's developper tools and simulating mobile devices, it works like a charm. However, when I view the website on any mobile device on any browser, the click/touch event doesn't seem to get registered. Here is the website link: http://aquaterratest.azurewebsites.net/

I have a Backbone app that uses rails API for the CRUD operations that it performs. Backbone views have events object that accepts event, selector and callback function like following:

window.fooView = Backbone.View.extend({ events: { 'click #back_btn': 'fooCallBackFunction' }, fooCallBackFunction: function() { // callback function } });

Now, I tried changing the first parameter, click to fastClick but it wouldn't work. What would I have to do to make this work?

At first it was working ok, but today I noticed it double firing the even on one touch. Sometimes this effect is even when I use chrome emulator on desktop computer.

jQuery allows the .live and .on functions for dynamically added elements to the DOM.

How can i use this ability with .fastClick? It doesn't seem to work out of the box. I will make a small donation for a fix :-)

When optimizing webstuff for mobile, we need to get around the 300ms delay by adding fastclick to our buttons. When the same page gets viewed on a desktop browser usually onclick handlers work better, because they are not selecting any text when pressing multiple times (desktop browsers interpret this as doubleclick to select text near the cursor).

hi there

when I have a button that I have a fastclick handler on, and I try to assign a new handler to it, the old one will remain and FastButtons onclick method will trigger twice (the old one and the new one).

This is because we don't unbind the old events when binding new ones. To solve this, we could either just unbind everything from the button before binding again or on the other hand, we might make some sort of .on .off behaviour to it.

what do you think?