This morning (Pacific Daylight Time) my webapp was successfully using CORS to make AJAX calls to a separate server, but about mid-morning the AJAX calls stopped working in Internet Explorer only. I had been referencing the CDN for Webix and changed the CDN address from edge to 2.3 after seeing that 2.4 was out but this didn’t change the behavior. I saw that there were some AJAX fixes in 2.4. Could this have caused some new issues with CORS support for IE?
When I’m monitoring network traffic from the tab with the webapp in it in Chrome I’m seeing an XMLHttpRequest being made, but when I try with IE I’m not even seeing a request start.
I’ve set up an example using webix.com/snippet. Here is the link http://webix.com/snippet/f79bce05. Press the button in anything except IE and you get JSON results back. If you press the button in IE you get a “script error” webix.message item. Any help would be appreciated.
I’ve changed the request to a POST instead of a GET (http://webix.com/snippet/2047ef57) to try and avoid Internet Explorer caching the results of an AJAX request and still get the “Script error” message when trying to make the AJAX call.
Hello,
I can confirm the problem in IE.
Our library creates ActiveXObject object for all IE versions. However, it is not a change of the latest version (all Webix versions use this approach).
You can try to use the following workaround for CORS in the latest IE:
Thank you Maria. In addition to your answer last night I also got a response from Stack Overflow (http://stackoverflow.com/questions/30494966/webix-ajax-with-cors-working-everywhere-except-ie?noredirect=1#comment49067660_30494966) where they noticed the ActiveXObject issue as well. They suggested overwriting the prototype, which I think I prefer in case I need to do anything else in this file that would be IE dependent. Thanks!