So, the fetch API is landing in Safari. I'm surprised, since the Safari implementation presumably still lacks the ability to abort a request as it does in Chrom

So, the fetch API is landing in Safari. I'm surprised, since the Safari implementation presumably still lacks the ability to abort a request as it does in Chrome. Since the discussion on how to resolve this issue is ongoing[1], I thought they'd wait until a decision was reached. Must be gearing up for Service Workers & Web Push — something I expected to be at the bottom of the priority list for Apple's browser. [1] https://github.com/whatwg/fetch/issues/27 https://github.com/whatwg/fetch/issues/27