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

Conflict with type range input #197

Open
filipealonso opened this issue Aug 18, 2020 · 2 comments
Open

Conflict with type range input #197

filipealonso opened this issue Aug 18, 2020 · 2 comments

Comments

@filipealonso
Copy link

Description of the bug
An input of type range has a draggable functionality to it which, while being used, shouldn't trigger a swiping event.

Steps to reproduce
Insert an type range input inside the parent component with the swipeable handlers and drag the input's "thumb" (left or right, if horizontal, or up and down, if vertical) to change the value.

Expected behavior
Swiping over the parent component should trigger a swiping event, but dragging the range input's "thumb" shouldn't.

@hartzis
Copy link
Collaborator

hartzis commented Aug 18, 2020

@filipealonso Thank you for the write up!

🤔 whoaa.. this is interesting.... If you could create an example we could see the bug in that would be incredibly helpful in debugging. You could fork the hook example here to get started hook example codesandbox.io

@silviogutierrez
Copy link

Same issue here. Any range input inside a swipeable container will trigger the swiping once you let go.

I tried event.stopPropagation in the onChange handler of the input, but no luck.

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

No branches or pull requests

3 participants