WebAssembly in Action

Author of the book "WebAssembly in Action"
Save 40% with the code: ggallantbl
The book's original source code can be downloaded from the Manning website and GitHub. The GitHub repository includes an updated-code branch that has been adjusted to work with the latest version of Emscripten (currently version 3.1.44).

Saturday, March 19, 2011

XMLHttpRequest calls when in IE 9 Standards mode

With Internet Explorer 10 (IE 10), the issue described in this article has been fixed if the browser is using IE 10 Standards Mode.

With all versions of Internet Explorer, even when IE becomes more standards compliant, there are usually workarounds that are still needed.

Even though IE 9 is the most standards compliant Microsoft browser to date, there are still several things that have been discovered that we need to be aware of.

Feature detection tests should always test for W3C features first and fall back to IE specific features if the W3C feature is unavailable. For example, the following would be the feature detection code to use to create an XML object from a string of XML:
function ConvertStringToXMLObject(sXML) {
// Test for W3C feature
if (DOMParser) {
var dpDOMParser = new DOMParser();
return dpDOMParser.parseFromString(sXML, "text/xml");
} else { // IE 8 and previous or IE 9 when *not* in Standards mode...
var xdDoc = new ActiveXObject("Microsoft.XMLDOM");
return xdDoc;

When Standards mode is on, IE 9 now supports the DOMParser object. The issue with this, however, is that the XMLHttpRequest object still returns an MSXML ActiveX object from the reponseXML property no matter which document compatibility mode IE 9 is using.

The MSXML ActiveX XML object is not compatible with the DOMParser XML object and will result in a 'Type mismatch' error if you try to append the one XML object to the other.

The workaround for this issue is to pass the responseText property, from your XMLHttpRequest object, to your client-side XML object creation function so that you get an XML object of the proper type as in the following example:
function MakeServerSideCall(sURL, sPostData) {
var xhrRequest = GetXMLHttpRequestObject();
xhrRequest.open("POST", sURL, false);

return ConvertStringToXMLObject(xhrRequest.responseText);

function GetXMLHttpRequestObject(){
var xhrRequest = null;

if (window.XMLHttpRequest) { xhrRequest = new XMLHttpRequest(); }
else if (window.ActiveXObject) { xhrRequest = new ActiveXObject("Microsoft.XMLHTTP"); }

return xhrRequest;

The following is a Microsoft article which talks about the DOMParser object, XMLSerializer object, as well as this workaround for the XMLHttpRequest object:

1 comment:

  1. GetXMLHttpRequestObject() method returns null object in IE9. Is it an inbuild function for Javascript??