Uncaught exception: CORS failures with responseType "document"

[taralx]

Testcase: http://taral.dreamhosters.com/eve-test/corsreject.html

Expected result "Result: FAILURE"
Actual result "Result: " and an uncaught exception in the console.

Browser: Google Chrome 24.0.1312.56 and 26.0.1398.0

[taralx]

Turns out this is from accessing responseText after a failed request. Might be a Chrome bug.

[taralx]

Okay, so XHR2 says this about responseText:

If responseType is not the empty string or "text", throw an "InvalidStateError" exception and terminate these steps.

So we should not access reponseText in this case.

[taralx]

Anyone know why we query responseText at all? Is it a compat thing?

[IgorMinar]

@taralx you are right: http://www.w3.org/TR/XMLHttpRequest/#dom-xmlhttprequest-responsetext

the responseText check is redundant and should be removed. some tests where we mock responseText will need to be changed as well.