-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
onEnded not being called in some conditions #496
Comments
Here are some URLs for reference: |
Seems like a duplicate of #471. The issue is that a browser does not deem a looping video to ever "end", which is technically true.. The only reason I don't know what we can do, other than maybe prevent |
Thanks for the reply and explanation. I managed to work around the behavior for my use case. The only reason I raised an issue is because the behavior is inconsistent between videos. I would suggest to at least put a small note in the callback prop documentation such as " Perhaps all videos could be looped by the same method (e.g. using Since Thank you again for the reply, and for working on this great and useful component! Please let me know if there is anything I can do to help. |
It doesn't make sense, as the video doesn't technically "end" Closes cookpete/react-player#496
It doesn't make sense, as the video doesn't technically "end" Closes cookpete/react-player#496
It doesn't make sense, as the video doesn't technically "end" Closes cookpete/react-player#496
It doesn't make sense, as the video doesn't technically "end" Closes cookpete/react-player#496
It doesn't make sense, as the video doesn't technically "end" Closes cookpete/react-player#496
It doesn't make sense, as the video doesn't technically "end" Closes cookpete/react-player#496
I have some video URLs that play fine, but the onEnded callback doesn't get called if loop is set to true.
Here's a reproduction (based on the standalone example):
https://jsfiddle.net/qv68yk2r/
If the loop attribute is removed, onEnded gets called as expected.
The text was updated successfully, but these errors were encountered: