-
Notifications
You must be signed in to change notification settings - Fork 51
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: hls.js regenerating after load #1031
Comments
It seems to be happening on the native player, so this is an even better reproducible example: https://codepen.io/endymion1818/pen/JoPKXRg |
thanks for the feedback @endymion1818. this does look like a hls.js issue though. is this causing any unexpected behavior or playback issues? |
It leads to rerenders which creates cumulative layout shift, so if the player is in the viewport it could result in site performance issues. My PO has noticed it and asked me to investigate it, I think they're worried the experience is a little jarring. It does look like a hls issue but I can't figure out what triggers it. We use JWPlayer currently and that doesn't seem to display the defect but it's currently using a very old version of hls.js, and they could have done other things to mask the behaviour. |
Sorry, deleted the example which uses |
Is there an existing issue for this?
Which Mux Elements/Packages does this apply to? Select all that apply
playback-core
Which browsers are you using?
Chrome, Firefox
Which operating systems are you using?
Other (add details below)
Description
I'm using this component via mux-video v0.22.0, After completing the full load, HLS.js seems to begin a new transmux session, I can't figure out what might be triggering it. Is there anything I can do to mitigate this issue? Why might it be doing this?
Reduced test case
https://codepen.io/endymion1818/pen/eYqXaYw
Steps to reproduce
Current Behavior
A new transmux session is initiated after load
Expected Behavior
Initial transmux session is not discarded and the player doesn't re-render
Errors
What version of the package are you using?
0.27.0
The text was updated successfully, but these errors were encountered: