Stream not playing on Safari but playing perfectly fine on chrome.
Open
Nobody has claimed this yet.
browser: Safari
Bug
Revisit-at-later-release-cycle
Stream Issue
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 2.8k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 27
Description
What version of Hls.js are you using?
14.2 and tested with latest version also.
What browser and OS are you using?
safari and macOS
Test stream:
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 on https://hls-js.netlify.com/demo and not just on my page
- The issue occurs in the latest client on https://hls-js-dev.netlify.com/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
- Play the above mentioned stream on safari using hls.js
Expected behavior
- Stream should play like it is playing perfectly on chrome and IE Edge.
Actual behavior
- Stream is not playing on safari
Console output
Paste the contents of the browser console here.
For media errors reported on Chrome browser, please also paste the output of chrome://media-internals
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the hls.js demo and the supplied M3U8 stream in Safari on macOS, then compare its behavior and console or media errors with Chrome. Trace the playback failure to the relevant Safari handling and verify the stream plays successfully in the demo without regressing other browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- audio-video-rtc, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100