-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Chrome browser: uncaught promise, when pausing/playing video #6998
Comments
👋 Thanks for opening your first issue here! 👋 If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
You can just ignore this error by catching the promise in most situation. In
Read carefully over play-request-was-interrupted. |
This is basically expected. We do try and silence these errors, but I guess the play toggle didn't silence the promise. |
Description
When playing a video on a slow connection in Chrome, e.g. https://videojs.com/advanced?video=disneys-oceans
It's possible that a uncaught promise is thrown in the javascript console when clicking pause/play while the video has not loaded yet.
Steps to reproduce
2.Start the video, and scrub/drag to the middle of the video
Results
Expected
No errors displayed in javascript console
Actual
Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22
Error output
Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22
Additional Information
Please include any additional information necessary here. Including the following:
versions
videojs
what version of videojs does this occur with?
We are using 7.11.0
Not sure what version runs on https://videojs.com/advanced/?video=disneys-oceans but i would assume the latest version?
browsers
Google Chrome Version 87.0.4280.88 (Official Build) (x86_64)
OSes
OSX Mojave
plugins
The text was updated successfully, but these errors were encountered: