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
There is a quirk in Safari explained in detail here(1): if the server doesn't respond correctly to the range header Safari sends, it sets the duration to infinite. I was bitten by this, as I serve audio from a custom backend to howler. Even if the audio isn't infinite, howler's end event will never run. I can fix my backend and will do so, but it would be great (and indeed, in line with its aspiration to support edge cases) if howler also defensively supported firing the end even with seemingly infinite-duration audio. I peeked the code quickly and it seems that the end event is currently only fired in accordance with the duration. I think that subscribing to the DOM ended event in case of infinite html5 audio will help to fix this edge case.
There is a quirk in Safari explained in detail here(1): if the server doesn't respond correctly to the range header Safari sends, it sets the duration to infinite. I was bitten by this, as I serve audio from a custom backend to howler. Even if the audio isn't infinite, howler's
end
event will never run. I can fix my backend and will do so, but it would be great (and indeed, in line with its aspiration to support edge cases) if howler also defensively supported firing theend
even with seemingly infinite-duration audio. I peeked the code quickly and it seems that theend
event is currently only fired in accordance with the duration. I think that subscribing to the DOMended
event in case of infinite html5 audio will help to fix this edge case.(1) http://stackoverflow.com/questions/9629223/audio-duration-returns-infinity-on-safari-when-mp3-is-served-from-php
The text was updated successfully, but these errors were encountered: