-
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
Changing source does not clear tracks #3000
Comments
Happy issue 3000. |
I haven't tried with non-m3u8 text tracks yet. I did try with non-native and that does the same. What do you mean with that html5 doesn't quite understand multi-video videos? Anyway, if we need to clear tracks manually that's not a problem, but currently the function is private. Maybe we should add a p.s. @ 3000 issues: party time! 🎂 |
By multi-video videos, I mean a "video"/player that plays more than a single video throughout the entire lifetime of the video/player. If it's just hls, specifically contrib-hls, then it's probably something that we need to do there assuming that safari handles this cleanup natively as well. As for remove track, we have a |
I was using Safari on Mac, so I didn't use contrib-hls at all. So I guess it is just in the html5 tech. Anyway, we use the same video element for multiple videos a lot and we didn't see any problems yet. We tested in IE9+, Safari, Firefox, Chrome and mobile browsers. It seems to work fine until now. Only that the tracks are not removed as described. |
Ah, I see. It's possibly a bug then that we don't clear out the native tracks properly from our emulated text track list. |
Ah need any help? I can try to make a PR if you provide some suggestions :) |
Always :) |
It seems that if I dynamically change the source of a video.js instance, it does not clear the text tracks.
If on an HLS-supported browser, this can easily be seen by doing the following javascript on videojs.com:
If I manually call
player.textTracks().removeTrack_
for all tracks it seems to work, but that seems like a private method.This seems to be the case for both native and emulated text tracks as far as I could find.
The text was updated successfully, but these errors were encountered: