@janhartmann perhaps you can take a look at this and make an initial pull request? Because this will break any xhr options I think.. cc @katspaugh
I might be interested, we are currently planning on changing a lot of functionality on how to fetch the audio from our services for the wavesurfer. Our issue is that we do not know the content length of the audio stream, so maybe by having the whole fetch api available within wavesurfer will aid us in this.
@entonbiba since we're going to release a 3.0.0 I suggest
XMLHTTPRequest with fetchOur issue is that we do not know the content length of the audio stream
fyi @janhartmann with the new fetch implementation in 3.0 your server needs to send a Content-Length header if you want to use the loading event (for progress bars etc).
Most helpful comment
I might be interested, we are currently planning on changing a lot of functionality on how to fetch the audio from our services for the wavesurfer. Our issue is that we do not know the content length of the audio stream, so maybe by having the whole fetch api available within wavesurfer will aid us in this.