Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pan/Swipe issues on mobile Chrome w/ overflow: auto children #1110

Closed
kirschre opened this issue May 16, 2017 · 1 comment
Closed

Pan/Swipe issues on mobile Chrome w/ overflow: auto children #1110

kirschre opened this issue May 16, 2017 · 1 comment

Comments

@kirschre
Copy link

Versions

Hammer.js 2.0.8, Chrome 58, Windows 7

Reproducer

https://codepen.io/kirschre/full/bWjoaJ

Steps

Open this page on Chrome mobile and attach a debugger - alternatively, open in Chrome, load developer tools (ctrl + shift + i), open device emulation mode (ctrl + shift + m). The reproducer just prints the names of swipe/pan events as they are generated. Click and drag (or swipe/pan) starting from the green area and observe the console output. Then, do the same actions, starting from the red area, and observe the console output.

Expected Behaviour

Swipe/pan events should behave the same way in each area, regardless of whether a child element has overflow: auto or not.

Observed Behaviour

Pan/Swipe events work as expected through the green area. In the regular desktop view, they work as expected in the red area as well. However, on mobile Chrome, and in desktop Chrome's mobile device view, events coming from the area with overflow property behave strangely. Swipe events don't seem to be fired ever, and pan events fire sporadically. Occasionally panend/pancancel will not fire after pan events. Hopefully I'm just missing something simple, but I haven't been able to find anything related in documentation/issues/SO.

@kirschre
Copy link
Author

Discovered I was missing touch-action on the child with overflow. Other problems still remain, but closing this as a duplicate of #1050 and #1056.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant