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

Stop Android treating swipe as tap #3514

Closed
wants to merge 1 commit into from

Conversation

mister-ben
Copy link
Contributor

Description

On Android, a short duration swipe is always considered a tap. Scrolling a page can easily start playback unintentionally - see #3157.

assign() returns {} in the touchstart handler, so touchDistance is always NaN in the touchmove handler.

It seems pageX, pageY etc are "own" properties of the Touch on iOS Safari (and of the object used in the tests) but not on Android Chrome, hence the difference in behaviour of assign().

Specific Changes proposed

Copy the specific properties needed instead of using assign(). Unless I'm missing something about the point of using assign() in the first place...

Requirements Checklist

  • Feature implemented / Bug fixed
  • Reviewed by Two Core Contributors

@gkatsev
Copy link
Member

gkatsev commented Aug 9, 2016

Looks good to me. Thanks for catching that @mister-ben!

@gkatsev gkatsev added confirmed patch This PR can be added to a patch release. labels Aug 9, 2016
@gkatsev gkatsev closed this in 2f5a0ca Aug 15, 2016
@outlawtorn
Copy link

I have this problem on firefox 50 and video.js 5.16.0 (laptop convertible to tablet)

akashta pushed a commit to hola/video.js that referenced this pull request Apr 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed patch This PR can be added to a patch release.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants