-
-
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
bug, dynamic update of <source(s)> and <track(s)> seems to be ignored #481
Comments
I'm currently trying to figure out how I can circumvent this bug. Any help greatly appreciated.. from MDN (https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement), I've seen we can reload the MediaElement:
Would it be possible in the library to call such a method on |
To see the effect in action: https://soluble.io/react-player/demo/ First click on 'Multiple Bunny' then 'Multiple Elephant' (elephant video loading will be ignored)... Repeat switching between them and you'll start seing:
|
#482 should fix it |
Took me a while to figure out, and it's not related to ReactPlayer but good to keep a note.
(update seems to affect Chrome too: play with effect https://soluble.io/react-player/demo/ (click multiple bunny then multiple elephant))
Setting new FilePlayer sources urls or tracks on an already loaded video does not actually reload the
<video> url
under Firefox (at least Firefox 61 - Ubuntu 18.04). Chromeworks as expecteddoes not work neither.Setting the video url as a string works, I'm referring specifically to multiple sources or tracks like:
To be sure I does not come from my code, I've updated the demo app.js to include 2 buttons with multiple sources. To reproduce: clone and yarn start https://github.com/belgattitude/react-player.git or see https://github.com/CookPete/react-player/compare/master...belgattitude:test-video-url-change-ignored?expand=1
Changing the source location from Firebug is also affected.
This bug is very annoying in my case, because video are loaded from a list... Props urls are well updated.
The text was updated successfully, but these errors were encountered: