You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Load the demo page https://hlsjs.video-dev.org/demo/?src=https%3A%2F%2Fstorage.googleapis.com%2Fshaka-demo-assets%2Fangel-one-widevine-hls%2Fhls.m3u8&demoConfig=eyJlbmFibGVTdHJlYW1pbmciOnRydWUsImF1dG9SZWNvdmVyRXJyb3IiOnRydWUsInN0b3BPblN0YWxsIjpmYWxzZSwiZHVtcGZNUDQiOmZhbHNlLCJsZXZlbENhcHBpbmciOi0xLCJsaW1pdE1ldHJpY3MiOi0xfQ== in the special chrome version
After a few seconds, click the detach media button
Would you like to submit a PR to avoid this escape, assuming that optional chaining resolves the exception described above media?.setMediaKeys(null)?.catch((error) => {?
Was media detached intentionally or is the exception described a result of tear-down after a larger compatibility related issue?
What version of Hls.js are you using?
1.5.14
What browser (including version) are you using?
Chrome38.x
What OS (including version) are you using?
Mac OS
Test stream
https://storage.googleapis.com/shaka-demo-assets/angel-one-widevine-hls/hls.m3u8
Configuration
Additional player setup steps
No response
Checklist
Steps to reproduce
https://hlsjs.video-dev.org/demo/?src=https%3A%2F%2Fstorage.googleapis.com%2Fshaka-demo-assets%2Fangel-one-widevine-hls%2Fhls.m3u8&demoConfig=eyJlbmFibGVTdHJlYW1pbmciOnRydWUsImF1dG9SZWNvdmVyRXJyb3IiOnRydWUsInN0b3BPblN0YWxsIjpmYWxzZSwiZHVtcGZNUDQiOmZhbHNlLCJsZXZlbENhcHBpbmciOi0xLCJsaW1pdE1ldHJpY3MiOi0xfQ==
in the special chrome versiondetach media
buttonExpected behaviour
No Error thrown
What actually happened?
Throw an error
catch in undefined
I guess it could be the line:
hls.js/src/controller/eme-controller.ts
Lines 1256 to 1259 in 01f50bb
media?.setMediaKeys(null)
returnundefined
here. We may remove thecatch
.Console output
Chrome media internals output
No response
The text was updated successfully, but these errors were encountered: