25215 2014-03-31 09:47:54 +0000 Tweak to example 1 and what element touch-action is applied to 2014-06-02 23:03:50 +0000 1 1 1 Unclassified PointerEventsWG Pointer Events specification unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 redux jrossi public-pointer-events public-pointer-events-bugzilla oldest_to_newest 103160 0 redux 2014-03-31 09:47:54 +0000 Currently, example 1 starts with <style> /* Disable intrinsic user agent touch behaviors (such as panning or zooming) so that all events are given to the application instead. */ html { touch-action: none; } </style> Personally, I find this a little heavy-handed and "dangerous". I've usually advocated applying touch-action (and before that, in touch events, preventDefault) more "surgically" just to the elements where it's needed, to avoid developers cargo-culting overly broad snippets of css/js that kill all browser defaults for everything. I'd suggest applying it just to the canvas element in this example. ... canvas { touch-action: none; } ... 107164 1 jrossi 2014-06-02 23:03:50 +0000 Really good bug to fix as IE and Chrome have been seeing compat issues with sites that apply touch-action to heavy handed. Fixed as suggested: https://dvcs.w3.org/hg/pointerevents/rev/c8ab8227ddcc