How to bind 'touchstart' and 'click

问题:

I\'m working on a mobile web site that has to work on a variety of devices. The one\'s giving me a headache at the moment are BlackBerry.

We need to support both keyboard clicks as well as touch events.

Ideally I\'d just use:

$thing.click(function(){...})

but the issue we\'re running into is that some of these blackberry devices have an very annoying delay from the time of the touch to it triggering a click.

The remedy is to instead use touchstart:

$thing.bind(\'touchstart\', function(event){...})

But how do I go about binding both events, but only firing one? I still need the click event for keyboard devices, but of course, don\'t want the click event firing if I\'m using a touch device.

A bonus question: Is there anyway to do this and additionally accommodate browsers that don\'t even have a touchstart event? In researching this, it looks like BlackBerry OS5 doesn\'t support touchstart so will also need to rely on click events for that browser.

ADDENDUM:

Perhaps a more comprehensive question is:

With jQuery, is it possible/recommended to handle both touch interactions and mouse interactions with the same bindings?

Ideally, the answer is yes. If not, I do have some options:

1) We use WURFL to get device info so could create our own matrix of devices. Depending on the device, we\'ll use touchstart OR click.

2) Detect for touch support in the browser via JS (I need to do some more research on that, but it seems like that is doable).

However, that still leaves one issue: what about devices that support BOTH. Some of the phones we support (namely the Nokias and BlackBerries) have both touch screens and keyboards. So that kind of takes me full circle back to the original question...is there a way to allow for both at once somehow?

回答1:

Update: Check out the jQuery Pointer Events Polyfill project which allows you to bind to \"pointer\" events instead of choosing between mouse & touch.

---

Bind to both, but make a flag so the function only fires once per 100ms or so.

var flag = false;
$thing.bind(\'touchstart click\', function(){
  if (!flag) {
    flag = true;
    setTimeout(function(){ flag = false; }, 100);
    // do something
  }

  return false
});

回答2:

This is the fix that I \"create\" and it take out the GhostClick and implements the FastClick. Try on your own and let us know if it worked for you.

$(document).on(\'touchstart click\', \'.myBtn\', function(event){
        if(event.handled === false) return
        event.stopPropagation();
        event.preventDefault();
        event.handled = true;

        // Do your magic here

});

回答3:

You could try something like this:

var clickEventType=((document.ontouchstart!==null)?\'click\':\'touchstart\');
$(\"#mylink\").bind(clickEventType, myClickHandler);

回答4:

Usually this works as well:

$(\'#buttonId\').on(\'touchstart click\', function(e){
    e.stopPropagation(); e.preventDefault();
    //your code here

});

回答5:

Just adding return false; at the end of the on(\"click touchstart\") event function can solve this problem.

$(this).on(\"click touchstart\", function() {
  // Do things
  return false;
});

From the jQuery documentation on .on()

Returning false from an event handler will automatically call event.stopPropagation() and event.preventDefault(). A false value can also be passed for the handler as a shorthand for function(){ return false; }.

回答6:

I had to do something similar. Here is a simplified version of what worked for me. If a touch event is detected, remove the click binding.

$thing.on(\'touchstart click\', function(event){
  if (event.type == \"touchstart\")
    $(this).off(\'click\');

  //your code here
});

In my case the click event was bound to an <a> element so I had to remove the click binding and rebind a click event which prevented the default action for the <a> element.

$thing.on(\'touchstart click\', function(event){
  if (event.type == \"touchstart\")
    $(this).off(\'click\').on(\'click\', function(e){ e.preventDefault(); });

  //your code here
});

回答7:

I succeeded by the following way.

Easy Peasy...

$(this).on(\'touchstart click\', function(e){
  e.preventDefault();
  //do your stuff here
});

回答8:

Generally you don\'t want to mix the default touch and non-touch (click) api. Once you move into the world of touch it easier to deal only with the touch related functions. Below is some pseudo code that would do what you want it to.

If you connect in the touchmove event and track the locations you can add more items in the doTouchLogic function to detect gestures and whatnot.

var touchStartTime;
var touchStartLocation;
var touchEndTime;
var touchEndLocation;

$thing.bind(\'touchstart\'), function() {
     var d = new Date();
     touchStartTime = d.getTime();
     touchStartLocation = mouse.location(x,y);
});

$thing.bind(\'touchend\'), function() {
     var d = new Date();
     touchEndTime= d.getTime();
     touchEndLocation= mouse.location(x,y);
     doTouchLogic();
});

function doTouchLogic() {
     var distance = touchEndLocation - touchStartLocation;
     var duration = touchEndTime - touchStartTime;

     if (duration <= 100ms && distance <= 10px) {
          // Person tapped their finger (do click/tap stuff here)
     }
     if (duration > 100ms && distance <= 10px) {
          // Person pressed their finger (not a quick tap)
     }
     if (duration <= 100ms && distance > 10px) {
          // Person flicked their finger
     }
     if (duration > 100ms && distance > 10px) {
          // Person dragged their finger
     }
}

回答9:

I believe the best practice is now to use:

$(\'#object\').on(\'touchend mouseup\', function () { });

touchend

The touchend event is fired when a touch point is removed from the touch surface.

The touchend event will not trigger any mouse events.

---

mouseup

The mouseup event is sent to an element when the mouse pointer is over the element, and the mouse button is released. Any HTML element can receive this event.

The mouseup event will not trigger any touch events.

EXAMPLE

$(\'#click\').on(\'mouseup\', function () { alert(\'Event detected\'); });
$(\'#touch\').on(\'touchend\', function () { alert(\'Event detected\'); });

<script src=\"https://ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js\"></script>
<h1 id=\"click\">Click me</h1>
<h1 id=\"touch\">Touch me</h1>

---

EDIT (2017)

As of 2017, browsers starting with Chrome and making steps towards making the click event .on(\"click\") more compatible for both mouse and touch by eliminating the delay generated by tap events on click requests.

This leads to the conclusion that reverting back to using just the click event would be the simplest solution moving forward.

I have not yet done any cross browser testing to see if this is practical.

回答10:

check fast buttons and chost clicks from google https://developers.google.com/mobile/articles/fast_buttons

回答11:

Well... All of these are super complicated.

If you have modernizr, it\'s a no-brainer.

ev = Modernizr.touch ? \'touchstart\' : \'click\';

$(\'#menu\').on(ev, \'[href=\"#open-menu\"]\', function(){
  //winning
});

回答12:

Another implementation for better maintenance. However, this technique will also do event.stopPropagation (). The click is not caught on any other element that clicked for 100ms.

var clickObject = {
    flag: false,
    isAlreadyClicked: function () {
        var wasClicked = clickObject.flag;
        clickObject.flag = true;
        setTimeout(function () { clickObject.flag = false; }, 100);
        return wasClicked;
    }
};

$(\"#myButton\").bind(\"click touchstart\", function (event) {
   if (!clickObject.isAlreadyClicked()) {
      ...
   }
}

回答13:

Just for documentation purposes, here\'s what I\'ve done for the fastest/most responsive click on desktop/tap on mobile solution that I could think of:

I replaced jQuery\'s on function with a modified one that, whenever the browser supports touch events, replaced all my click events with touchstart.

$.fn.extend({ _on: (function(){ return $.fn.on; })() });
$.fn.extend({
    on: (function(){
        var isTouchSupported = \'ontouchstart\' in window || window.DocumentTouch && document instanceof DocumentTouch;
        return function( types, selector, data, fn, one ) {
            if (typeof types == \'string\' && isTouchSupported && !(types.match(/touch/gi))) types = types.replace(/click/gi, \'touchstart\');
            return this._on( types, selector, data, fn);
        };
    }()),
});

Usage than would be the exact same as before, like:

$(\'#my-button\').on(\'click\', function(){ /* ... */ });

But it would use touchstart when available, click when not. No delays of any kind needed :D

回答14:

I just came up with the idea to memorize if ontouchstart was ever triggered. In this case we are on a device which supports it and want to ignore the onclick event. Since ontouchstart should always be triggered before onclick, I\'m using this:

<script> touchAvailable = false; </script>
<button ontouchstart=\"touchAvailable=true; myFunction();\" onclick=\"if(!touchAvailable) myFunction();\">Button</button>

回答15:

You could try like this:

var clickEvent = ((\'ontouchstart\' in document.documentElement)?\'touchstart\':\'click\');
$(\"#mylink\").on(clickEvent, myClickHandler);

回答16:

This worked for me, mobile listens to both, so prevent the one, which is the touch event. desktop only listen to mouse.

 $btnUp.bind(\'touchstart mousedown\',function(e){
     e.preventDefault();

     if (e.type === \'touchstart\') {
         return;
     }

     var val = _step( _options.arrowStep );
               _evt(\'Button\', [val, true]);
  });

回答17:

In my case this worked perfectly:

jQuery(document).on(\'mouseup keydown touchend\', function (event) {
var eventType = event.type;
if (eventType == \'touchend\') {
    jQuery(this).off(\'mouseup\');
}
});

The main problem was when instead mouseup I tried with click, on touch devices triggered click and touchend at the same time, if i use the click off, some functionality didn\'t worked at all on mobile devices. The problem with click is that is a global event that fire the rest of the event including touchend.

回答18:

I am also working on an Android/iPad web app, and it seems that if only using \"touchmove\" is enough to \"move components\" ( no need touchstart ). By disabling touchstart, you can use .click(); from jQuery. It\'s actually working because it hasn\'t be overloaded by touchstart.

Finally, you can binb .live(\"touchstart\", function(e) { e.stopPropagation(); }); to ask the touchstart event to stop propagating, living room to click() to get triggered.

It worked for me.

回答19:

There are many things to consider when trying to solve this issue. Most solutions either break scrolling or don\'t handle ghost click events properly.

For a full solution see https://developers.google.com/mobile/articles/fast_buttons

NB: You cannot handle ghost click events on a per-element basis. A delayed click is fired by screen location, so if your touch events modify the page in some way, the click event will be sent to the new version of the page.

回答20:

It may be effective to assign to the events \'touchstart mousedown\' or \'touchend mouseup\' to avoid undesired side-effects of using click.

回答21:

Taking advantage of the fact that a click will always follow a touch event, here is what I did to get rid of the \"ghost click\" without having to use timeouts or global flags.

$(\'#buttonId\').on(\'touchstart click\', function(event){
    if ($(this).data(\"already\")) {
        $(this).data(\"already\", false);
        return false;
    } else if (event.type == \"touchstart\") {
        $(this).data(\"already\", true);
    }
    //your code here
});

Basically whenever an ontouchstart event fires on the element, a flag a set and then subsequently removed (and ignored), when the click comes.

回答22:

Why not use the jQuery Event API?

http://learn.jquery.com/events/event-extensions/

I\'ve used this simple event with success. It\'s clean, namespaceable and flexible enough to improve upon.

var isMobile = /Android|webOS|iPhone|iPad|iPod|BlackBerry/i.test(navigator.userAgent);
var eventType = isMobile ? \"touchstart\" : \"click\";

jQuery.event.special.touchclick = {
  bindType: eventType,
  delegateType: eventType
};

回答23:

If you are using jQuery the following worked pretty well for me:

var callback; // Initialize this to the function which needs to be called

$(target).on(\"click touchstart\", selector, (function (func){
    var timer = 0;
    return function(e){
        if ($.now() - timer < 500) return false;
        timer = $.now();
        func(e);
    }
})(callback));

Other solutions are also good but I was binding multiple events in a loop and needed the self calling function to create an appropriate closure. Also, I did not want to disable the binding since I wanted it to be invoke-able on next click/touchstart.

Might help someone in similar situation!

回答24:

For simple features, just recognize touch or click I use the following code:

var element = $(\"#element\");

element.click(function(e)
{
  if(e.target.ontouchstart !== undefined)
  {
    console.log( \"touch\" );
    return;
  }
  console.log( \"no touch\" );
});

This will return \"touch\" if the touchstart event is defined and \"no touch\" if not. Like I said this is a simple approach for click/tap events just that.

回答25:

I am trying this and so far it works (but I am only on Android/Phonegap so caveat emptor)

  function filterEvent( ob, ev ) {
      if (ev.type == \"touchstart\") {
          ob.off(\'click\').on(\'click\', function(e){ e.preventDefault(); });
      }
  }
  $(\'#keypad\').on(\'touchstart click\', \'.number, .dot\', function(event) {
      filterEvent( $(\'#keypad\'), event );
      console.log( event.type );  // debugging only
           ... finish handling touch events...
  }

I don\'t like the fact that I am re-binding handlers on every touch, but all things considered touches don\'t happen very often (in computer time!)

I have a TON of handlers like the one for \'#keypad\' so having a simple function that lets me deal with the problem without too much code is why I went this way.

回答26:

Being for me the best answer the one given by Mottie, I\'m just trying to do his code more reusable, so it\'s my contribution:

bindBtn (\"#loginbutton\",loginAction);

function bindBtn(element,action){

var flag = false;
$(element).bind(\'touchstart click\', function(e) {
    e.preventDefault();
    if (!flag) {
        flag = true;
        setTimeout(function() {
            flag = false;
        }, 100);
        // do something
        action();
    }
    return false;
});

回答27:

Try to use Virtual Mouse (vmouse) Bindings from jQuery Mobile. It\'s virtual event especially for your case:

$thing.on(\'vclick\', function(event){ ... });

http://api.jquerymobile.com/vclick/

Browser support list: http://jquerymobile.com/browser-support/1.4/

回答28:

EDIT: My former answer (based on answers in this thread) was not the way to go for me. I wanted a sub-menu to expand on mouse enter or touch click and to collapse on mouse leave or another touch click. Since mouse events normally are being fired after touch events, it was kind of tricky to write event listeners that support both touchscreen and mouse input at the same time.

jQuery plugin: Touch Or Mouse

I ended up writing a jQuery plugin called \"Touch Or Mouse\" (897 bytes minified) that can detect whether an event was invoked by a touchscreen or mouse (without testing for touch support!). This enables the support of both touchscreen and mouse at the same time and completely separate their events.

This way the OP can use touchstart or touchend for quickly responding to touch clicks and click for clicks invoked only by a mouse.

Demonstration

First one has to make ie. the body element track touch events:

$(document.body).touchOrMouse(\'init\');

Mouse events our bound to elements in the default way and by calling $body.touchOrMouse(\'get\', e) we can find out whether the event was invoked by a touchscreen or mouse.

$(\'.link\').click(function(e) {
  var touchOrMouse = $(document.body).touchOrMouse(\'get\', e);

  if (touchOrMouse === \'touch\') {
    // Handle touch click.
  }
  else if (touchOrMouse === \'mouse\') {
    // Handle mouse click.
  }
}

See the plugin at work at http://jsfiddle.net/lmeurs/uo4069nh.

Explanation

1. This plugin needs to be called on ie. the body element to track touchstart and touchend events, this way the touchend event does not have to be fired on the trigger element (ie. a link or button). Between these two touch events this plugin considers any mouse event to be invoked by touch.
2. Mouse events are fired only after touchend, when a mouse event is being fired within the ghostEventDelay (option, 1000ms by default) after touchend, this plugin considers the mouse event to be invoked by touch.
3. When clicking on an element using a touchscreen, the element gains the :active state. The mouseleave event is only fired after the element loses this state by ie. clicking on another element. Since this could be seconds (or minutes!) after the mouseenter event has been fired, this plugin keeps track of an element\'s last mouseenter event: if the last mouseenter event was invoked by touch, the following mouseleave event is also considered to be invoked by touch.

回答29:

Here\'s a simple way to do it:

// A very simple fast click implementation
$thing.on(\'click touchstart\', function(e) {
  if (!$(document).data(\'trigger\')) $(document).data(\'trigger\', e.type);
  if (e.type===$(document).data(\'trigger\')) {
    // Do your stuff here
  }
});

You basically save the first event type that is triggered to the \'trigger\' property in jQuery\'s data object that is attached to the root document, and only execute when the event type is equal to the value in \'trigger\'. On touch devices, the event chain would likely be \'touchstart\' followed by \'click\'; however, the \'click\' handler won\'t be executed because \"click\" doesn\'t match the initial event type saved in \'trigger\' (\"touchstart\").

The assumption, and I do believe it\'s a safe one, is that your smartphone won\'t spontaneously change from a touch device to a mouse device or else the tap won\'t ever register because the \'trigger\' event type is only saved once per page load and \"click\" would never match \"touchstart\".

Here\'s a codepen you can play around with (try tapping on the button on a touch device -- there should be no click delay): http://codepen.io/thdoan/pen/xVVrOZ

I also implemented this as a simple jQuery plugin that also supports jQuery\'s descendants filtering by passing a selector string:

// A very simple fast click plugin
// Syntax: .fastClick([selector,] handler)
$.fn.fastClick = function(arg1, arg2) {
  var selector, handler;
  switch (typeof arg1) {
    case \'function\':
      selector = null;
      handler = arg1;
      break;
    case \'string\':
      selector = arg1;
      if (typeof arg2===\'function\') handler = arg2;
      else return;
      break;
    default:
      return;
  }
  this.on(\'click touchstart\', selector, function(e) {
    if (!$(document).data(\'trigger\')) $(document).data(\'trigger\', e.type);
    if (e.type===$(document).data(\'trigger\')) handler.apply(this, arguments);
  });
};

Codepen: http://codepen.io/thdoan/pen/GZrBdo/

回答30:

The best method I have found is to write the touch event and have that event call the normal click event programatically. This way you have all your normal click events and then you need to add just one event handler for all touch events. For every node you want to make touchable, just add the \"touchable\" class to it to invoke the touch handler. With Jquery it works like so with some logic to make sure its a real touch event and not a false positive.

$(\"body\").on(\"touchstart\", \".touchable\", function() { //make touchable  items fire like a click event
var d1 = new Date();
var n1 = d1.getTime();
setTimeout(function() {
    $(\".touchable\").on(\"touchend\", function(event) {
        var d2 = new Date();
        var n2 = d2.getTime();
        if (n2 - n1 <= 300) {
            $(event.target).trigger(\"click\"); //dont do the action here just call real click handler
        }
    });
}, 50)}).on(\"click\", \"#myelement\", function() {
//all the behavior i originally wanted
});