`touch-action:none` prevents scrolling on some mobile devices about hammer-time HOT 2 CLOSED

This problem happens on browsers where touch-action is supported... meaning, the hammer-time polyfill isn't causing it. It's just touch-action:none; working "as expected".

Looking at the specs for this property, it's understandable that scrolling is disabled:

• https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action
• http://www.w3.org/TR/pointerevents/#the-touch-action-css-property

This makes me wonder, is it a good idea to use hammer-time as a polyfill for touch-action: none;? I'm not using hammer-time in a desire to disable scrolling (or any other default behaviors). I just want to eliminate the 300ms delay (which hammer time does a pretty good job at).

from hammer-time.

@bryanbraun touch action is the built in standards way browsers allow you to remove the 300ms delay. Hammer time polyfills the relevant parts of the css property to make it so you can use this in all browsers today. As a polyfill we hope that hammer time wont be necessary in the future :-).

The fact that touch-action affects scrolling is necessary and intentional for this to cover cases of things like double tap to zoom, double tap to scroll ( many people don't know about this in ios ) and to allow better control over what events are emitted in a performant way.

Im going to close this since this is the intentional behivor

from hammer-time.