-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fix: Correct playhead when seek beyond seekRange #6304
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
@CeilingFANC please sign the CLA! Thanks! |
Incremental code coverage: 100.00% |
@CeilingFANC, this is failing tests on all platforms. You can run the tests yourself with |
Closing due to inactivity. If the author would like to continue this PR, they can reopen it (preferred) or start a new one (if needed). |
@CeilingFANC I reopened it |
@CeilingFANC Please, rebase! |
Fixes #5202 --------- Co-authored-by: Álvaro Velad Galván <[email protected]>
Fixes #5202 --------- Co-authored-by: Álvaro Velad Galván <[email protected]>
This PR has been identified as the cause of seeking-related bugs in the Cast Application Framework, affecting v4.7.13, v4.8.0, and v4.8.1. I will revert this PR and reopen the associated issue. The reverted PR will appear in v4.7.14 and v4.8.2. |
PR shaka-project#6304 caused seeking timeouts in Cast Application Framework, in v4.7.13, v4.8.0, and v4.8.1. Reverts "fix: Correct playhead when seek beyond seekRange (shaka-project#6304)" This reverts commit f91188e. Reopens shaka-project#5202
Reverted by #6539 |
Use recurring timer to correct playhead when time is beyond seekRange.
Fixes #5202