close() doesn't terminate the connection when fetch is being used about eventsource HOT 2 CLOSED

Yeah but if the polyfill is just discarding the response the http connection will still be active I'm assuming and the EventSource close() method still wouldn't be closing the stream.

Without this fix my only way to recover from the queueing of the connections (after 6) was to make the drastic call to something like window.stop() so that I could remove the old connection and start a new one (that has many other implications though). My application needs to be able to create and close EventSources on demand (that are all hosted at the same origin), each time I switch to a different stream I close the previous expecting it to actually close the connection (like the native EventSource does without the npm package) but it wasn't.

from eventsource.

Fetch now support to be aborted in Firefox and Edge, and there's a polyfill that for Chrome and Safari... although the polyfill just only discard the response, but it's something :-)

from eventsource.