-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
A second loadSource call autoplays primary content immediately. #6839
Labels
Bug
Confirmed
Interstitials
Verify Fixed
An unreleased bug fix has been merged and should be verified before closing.
Milestone
Comments
matvp91
added
Bug
Needs Triage
If there is a suspected stream issue, apply this label to triage if it is something we should fix.
labels
Nov 12, 2024
robwalch
added
Confirmed
Interstitials
and removed
Needs Triage
If there is a suspected stream issue, apply this label to triage if it is something we should fix.
labels
Nov 12, 2024
Adding Interstitials label even though this is reproducible without Interstitials in the HLS asset. The running theory is that the play() calls in the Interstitial controller are responsible:
Setting |
matvp91
added a commit
to matvp91/hls.js
that referenced
this issue
Nov 18, 2024
robwalch
pushed a commit
that referenced
this issue
Nov 18, 2024
3 tasks
robwalch
added
the
Verify Fixed
An unreleased bug fix has been merged and should be verified before closing.
label
Nov 18, 2024
robwalch
removed
the
Verify Fixed
An unreleased bug fix has been merged and should be verified before closing.
label
Nov 29, 2024
robwalch
added a commit
that referenced
this issue
Nov 30, 2024
- Improve blocking requests with parts and low-latency mode disabled - Defer autostart until after manifest loasded and level loaded when media playlist is source Fixes #6858 Interstitial startup fixes - Added `hls.loadingEnabled` getter - Do not call startLoad when stopped and do not resume primary on first item Fixes #6839 (cherry picked from commit 5f2cde23288d70297ac97f85620b11f346755d4c)
robwalch
added a commit
that referenced
this issue
Nov 30, 2024
- Improve blocking requests with parts and low-latency mode disabled - Defer autostart until after manifest loasded and level loaded when media playlist is source Fixes #6858 Interstitial startup fixes - Added `hls.loadingEnabled` getter - Do not call startLoad when stopped and do not resume primary on first item Fixes #6839
3 tasks
github-project-automation
bot
moved this from In Progress
to Done
in HLS.js Interstitials
Dec 3, 2024
robwalch
added
the
Verify Fixed
An unreleased bug fix has been merged and should be verified before closing.
label
Dec 3, 2024
Just merged #6879 into dev: https://hlsjs-dev.video-dev.org/demo/ Two changes relative to this issue:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
Confirmed
Interstitials
Verify Fixed
An unreleased bug fix has been merged and should be verified before closing.
What version of Hls.js are you using?
v1.6.0-beta
What browser (including version) are you using?
Chrome
What OS (including version) are you using?
macOS
Test stream
No response
Configuration
Additional player setup steps
This is a regression compared to v1.5.
A sample with v1.5: https://stackblitz.com/edit/vitejs-vite-fkf2xf
A sample with v1.6-beta: https://stackblitz.com/edit/vitejs-vite-tohum2
The same steps to reproduce result in different behavior, with v1.5 not starting the asset (as it requires a user gesture), but v1.6 does.
Checklist
Steps to reproduce
Expected behaviour
A subsequent loadSource call should not start playback when no
autoplay
attribute is present.What actually happened?
A subsequent loadSource call starts playback immediately, with
autoplay
not present on the video element.Console output
Chrome media internals output
No response
The text was updated successfully, but these errors were encountered: