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
Hi @trek et al, thanks a lot for your work on this.
We recently started using pretender as part of ember-cli-mirage in our Ember app and noticed that our HLS videos are not playing correctly anymore in development.
We have a passthrough rule in our mirage config for the domain where we load our HLS manifest files from and you can see them correctly being loaded in the network pane of the Chrome devtools, but HLS.js (the library we use) is still throwing a manifestLoadTimeOut error.
Investigation indicates that HLS.js is simply not clearing its internal timeout because the onloadend event is never called for the request.
It only happens in our development environment and HLS.js just seems to have moved to using onreadystatechange (dailymotion/hls.js@55cabcf), so it is not criticial, but I wanted to report the issue anyway.
We are using mirage 0.2.1, pretender 1.1.0, and FakeXMLHttpRequest 1.4.0
Let me know if there are additional information that would be helpful for you.
The text was updated successfully, but these errors were encountered:
Hi @trek et al, thanks a lot for your work on this.
We recently started using pretender as part of ember-cli-mirage in our Ember app and noticed that our HLS videos are not playing correctly anymore in development.
We have a passthrough rule in our mirage config for the domain where we load our HLS manifest files from and you can see them correctly being loaded in the network pane of the Chrome devtools, but HLS.js (the library we use) is still throwing a
manifestLoadTimeOut
error.Investigation indicates that HLS.js is simply not clearing its internal timeout because the
onloadend
event is never called for the request.It only happens in our development environment and HLS.js just seems to have moved to using
onreadystatechange
(dailymotion/hls.js@55cabcf), so it is not criticial, but I wanted to report the issue anyway.We are using mirage
0.2.1
, pretender1.1.0
, and FakeXMLHttpRequest1.4.0
Let me know if there are additional information that would be helpful for you.
The text was updated successfully, but these errors were encountered: