-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
When seekOnTaps is on, the right and left parts of the screen are blocked to play/pause on single taps #8199
Comments
@avelad I believe there’s room for improvement with this approach. When scrolling, if the tap ends within the player’s tap area, the system eventually interprets the tap as a pause or play command rather than recognizing it as part of a scroll. This issue occurs only in the seekOnTaps areas; in the middle of the video, the system correctly distinguishes between a tap and a scroll. |
@avelad Sorry, shall I create another report in a separate post, or here is ok? |
@avelad I was doing some tries to achieve a similar effect on another code and playing around, and I came to this solution: What do you think of an approach like this, where we track where the event started, where it ended, so if its more than a delta, we consider it a click vs a scroll?
|
Do you want create a PR with it? |
I am getting errors due to and title not matching, would it be possible for you at least to take a look, and PR yourself? |
This issue can be reproduced in the demos. When seekOnTaps is enabled, the left and right sides of the player become unresponsive to single-tap play/pause commands. I would expect propagation to stop only when a double tap occurs within a short time frame or the visual controller for seekOnTap is already visible. If, for example, 500 ms have already passed and the seekOnTap visual interface is not enabled, the play/pause command should be executed. The current behavior with seekOnTaps enabled might be unintuitive and disturbing to the end user.
The text was updated successfully, but these errors were encountered: