Neither then() nor catch() executed when request timeout in Safari

[fabioberger]

In Safari V9.0.3 (10601.4.4), neither then() nor catch() is called when a request timeout occurs. Instead, Safari prints out the following error to the console:

In Chrome V49.0.2623.87 (64-bit), the catch() callback is properly executes as expected.

Test Script Used:

fetch('http://10.255.255.1') // a non-routable IP address
    .then(function(response) {
        console.log("response.ok", response.ok);
    }).catch(function(error) {
        console.log('Failed: ', error)
    });

Without either then() or catch() being called on timeout, how are we supposed to handle this type of request failure for Safari browsers?

[mislav]

Thanks for bringing this to our attention. This seems to be a limitation of XMLHttpRequest in Safari. I'm not sure if there's something we can do about this, but on your end you can definitely install an ad-hoc timeout like suggested here. This will at least ensure that non-routable requests eventually get rejected.

[fabioberger]

Thanks for the quick response Mislav, I've gone ahead and filed a bug report for the Safari team at Apple and in the mean time will implement the timeout as you suggested.

[dgraham]

@mislav I think this is asking for:

xhr.ontimeout = function() {
  reject(new Error('timeout'))
}

so that the promise is not trapped in the pending state.

@fabioberger What is the error object returned by Chrome and Firefox in your catch example?

[fabioberger]

@dgraham The error returned from the catch in Chrome is:

TypeError: Failed to fetch
    at TypeError (native)

Full console output: