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

Pause transcript auto-scroll on mobile devices when user is scrolling through transcript content #363

Open
4 tasks
elynema opened this issue Jan 26, 2024 · 4 comments

Comments

@elynema
Copy link

elynema commented Jan 26, 2024

Description

For the transcript in Chrome on iPad, when you try to scroll in the transcript tab for the first time, the auto-scroll fights you trying to take you back to the current spot in the transcript. If you have scrolled around in the transcript tab to select another starting point, the auto-scroll of transcript stops working.

In the current implementation, transcript component stops auto scrolling when the mouse pointer is hovering over the transcript content (when user is actively scrolling the transcript content), which doesn't have an equivalent implementation for touch devices but we probably should.

This could be the reason for auto scroll breaking when interacting with the transcript component on iPads.

Done Looks Like

  • Behavior should match desktop web browser - when a user scrolls through the transcript content, auto-scroll should pause so the transcript isn't jumping around
  • When the user stops scrolling in the transcript content (stops touching?), auto-scroll should jump the transcript back to currently playing spot
  • Tested on Android in Chrome
  • Tested on iPad Chrome and Safari
@joncameron
Copy link
Contributor

Touch handlers will need to be added to the Transcript component.

1 similar comment
@joncameron
Copy link
Contributor

Touch handlers will need to be added to the Transcript component.

@joncameron
Copy link
Contributor

Needs retesting; auto-scroll option is now available in the transcript component, and this is probably sufficient to satisfy this case.

@joncameron
Copy link
Contributor

Are we satisfied with the current behavior?

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

2 participants