-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Open
Labels
EnhancementRevisit-at-later-release-cycleWill revisit during release cycle indicated by the MilestoneWill revisit during release cycle indicated by the Milestone
Milestone
Description
What version of Hls.js are you using?
v1.5.20
What browser (including version) are you using?
safari
What OS (including version) are you using?
iphone, ios
Test stream
No response
Configuration
{}Additional player setup steps
No response
Checklist
- The issue observed is not already reported by searching on Github under https://github.com/video-dev/hls.js/issues
- The issue occurs in the stable client (latest release) on https://hlsjs.video-dev.org/demo and not just on my page
- The issue occurs in the latest client (main branch) on https://hlsjs-dev.video-dev.org/demo and not just on my page
- The stream has correct Access-Control-Allow-Origin headers (CORS)
- There are no network errors such as 404s in the browser console when trying to play the stream
Steps to reproduce
- Open the HLS.js player in Safari on an iPhone and start playing an HLS stream.
- Background the Safari browser, allowing the device to automatically lock and turn off the screen.
- Stop the OBS stream and wait for a few minutes.
- Reopen Safari and return to the HLS.js player.
Expected behaviour
After reopening Safari, the player should detect that the stream has stopped and throw an error event.
What actually happened?
The player remains in a loading state indefinitely without throwing any error event, even though the stream has stopped.
Console output
not error eventChrome media internals output
Metadata
Metadata
Assignees
Labels
EnhancementRevisit-at-later-release-cycleWill revisit during release cycle indicated by the MilestoneWill revisit during release cycle indicated by the Milestone
Type
Projects
Status
Top priorities