Re: [whatwg/fetch] what should fetch() do if request's window has been destroyed or stopped? (#153)

Similar to the user pressing the stop button, aborted media requests seem to have inconsistent behavior in browsers today.

Suppose you have an `Audio` object pointed at `https://example.com/some-live-stream`.  The live stream is a live HTTP progressive stream that has indefinite length.  Now, suppose you have a service worker:

```
self.addEventListener('fetch', (e) => {
  e.respondWith(fetch(e.request));
}
```

Now, kill the audio src:

```
audio.src = '';
```

On Chrome, the audio stream request is cancelled, which is what I would expect.  On Safari, the request keeps on going.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/153#issuecomment-576827903

Received on Tuesday, 21 January 2020 18:57:36 UTC