Use maxTouchPoints instead of navigator.pointerEnabled

Question

Use maxTouchPoints instead of navigator.pointerEnabled

seb-pereira opened this issue 11 years ago · comments

Sebastien Pereira commented 11 years ago

navigator.pointerEnabled is removed from the spec [1]
Feature detection https://github.com/ibm-js/dpointer/blob/master/events.js#L17 should rely on navigator.maxTouchPoints [2]

[1] http://www.w3.org/2013/11/19-pointerevents-minutes.html#item04
[2] https://dvcs.w3.org/hg/pointerevents/raw-file/c16e5fe3ff87/pointerEvents.html#extensions-to-the-navigator-interface

Sebastien Pereira · Answer 1 · Mon Sep 08 2014 23:15:54 GMT+0800 (China Standard Time)

Actually, support for Pointer Events should be detected using "onpointerdown" in document.

maxTouchPoints is not accurate because it can be defined while events are not supported, this is the case with Chrome 35+ which supports the touch-action CSS property and defines maxTouchPoints but doesn't emit pointer events.