3 ms·
IE has been basically standards-compliant for XHR since IE9, and possibly before: http://www.w3.org/TR/XMLHttpRequest/#interface-xmlhttprequest http://www.w3.o
by nostrademons 13y ago
IE has been basically standards-compliant for XHR since IE9, and possibly before:
http://www.w3.org/TR/XMLHttpRequest/#interface-xmlhttprequest http://www.w3.org/TR/XMLHttpRequest/#interface-xmlhttpreques...
http://msdn.microsoft.com/en-us/library/ie/ms535874(v=vs.85).aspx http://msdn.microsoft.com/en-us/library/ie/ms535874(v=vs.85)...
- voltagex_ 13y agoFor IE9, don't you need IE-specific code for cross domain requests?
- nostrademons 13y agoYeah, you need XDomainRequest for CORS requests in IE8 and 9. IE10 is fully standards-compliant. http://blogs.msdn.com/b/ieinternals/archive/2010/05/13/xdomainrequest-restrictions-limitations-and-workarounds.aspx http://blogs.msdn.com/b/ieinternals/archive/2010/05/13/xdoma...
- btd 13y agoIt is very castrated, better to use hidden iframe + window.postMessage for cors in ie8 and ie9.
- duncans 13y agoI don't think "castrated" is the word you meant :-) Perhaps "constrained" or "restricted"
- Dylan16807 13y ago...why not? "to render impotent or deprive of vitality"
- kishor_gurtu 13y agoFunny, because IE invented XHR.