Stop trying to detect touch and mobile devices

[david-mark]

There's absolutely no point in trying to pigeonhole devices as "touch", "touch only", etc. Not only impossible, but pointless (no puns intended). Proper pointer event handling makes no such assumptions and browser scripts should never reference the UA string.

const MOBILE_REGEX = /mobile|tablet|ip(ad|hone|od)|android/i;

const SUPPORT_TOUCH = ('ontouchstart' in window);
const SUPPORT_POINTER_EVENTS = prefixed(window, 'PointerEvent') !== undefined;
const SUPPORT_ONLY_TOUCH = SUPPORT_TOUCH && MOBILE_REGEX.test(navigator.userAgent);

Attach both touch and pointer listeners and deal with them in turn. No need to try to predict which will fire.

[grumpygary]

add:
delete window.PointerEvent;
in your index.html PRIOR to loading hammer.js, and it will ignore those events.
You can also set SUPPORT_POINTER_EVENTS = false; (line 384 of v2.0.8) to do the same thing.
Ideally the devs would add the ability to turn this off, but so goes the open source dilemma...

[david-mark]

Or, you could fix the described issue with the code. 🙂 Trying to delete a host object is silly (and might just throw an exception), so libraries can't rely on users doing that.

…

On Wed, Nov 29, 2017, 3:14 PM Gary Skiba ***@***.***> wrote: add: delete window.PointerEvent; in your index.html PRIOR to loading hammer.js, and it will ignore those events. You can also set SUPPORT_POINTER_EVENTS = false; (line 384 of v2.0.8) to do the same thing. Ideally the devs would add the ability to turn this off, but so goes the open source dilemma... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1067 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AArScbNmJQG3laXWrwj5XeOhXJy1CMowks5s7bshgaJpZM4Lr3XW> .