Material's custom swipe recognizer sets touch-action: none

[jelbourn]

The custom recognizers in GestureConfig are causing touch-action: none to always be added to elements with any hammer event. This is problematic because it will prevent normal scrolling. The swipe recognizer seems to be the culprit (with both pan-y and pan-x actions being tied to the recognizer, even though we only want pan-y)

We should probably only be adding recognizers that correspond to the events being listened for. This would require a (non-breaking) change in @angular/platform-browser to pass the event name to the buildHammer function.

[kheiligh]

for me - i was able to fix this with
Hammer.defaults.touchAction = 'pan-y'; to get scrolling working, and (swiperight) and (swipeleft) still work fine

[intellix]

Got this after updating to Angular 9 and this fixed it for us: hammerjs/hammer.js#1014 (comment)

Was originally going to go for this which worked too:

.my-thing {
  touch-action: pan-y !important;
}

[jelbourn]

Closing this since we have completely removed all HammerJS code in v10.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}