JavaScript 2.0-The Complete Reference, Second ... - freecodingtutorial

xmldoc.async = false;
xmldoc.load("staff.xml");
Obviously, with the use of an if statement we could make the previous example work in both
browsers.
if (window.ActiveXObject)
var xmldoc=new ActiveXObject("Microsoft.XMLDOM");
else if
(document.implementation&&document.implementation.createDocument)
xmldoc=document.implementation.createDocument("","doc",null);
xmldoc.async = false;
xmldoc.load("staff.xml");
We leave it to the reader to make this modification to the previous example to make it crossbrowser.
However, take notice of the fact that once again differences abound as Mozilla
represents whitespace in its DOM tree and doesn‘t like to load the document initially. Just click
the provided ―Redisplay XML Document‖ button.
While it would seem from the previous paragraphs that Mozilla and IE aren‘t far apart, that isn‘t
quite true as Mozilla provides the possibility of directly using XML and bringing in (X)HTML. IE
can handle something like this but not very cleanly, as we‘ll see.
In this particular example, we will use XML directly rather than XML accessed via an (X)HTML
document. Because of this, we do not require a special XMLDocument object; instead, we
reference the Document object just as we would expect. For example, to print out the
nodeName property of the root element we would use
alert(document.documentElement.nodeName)
However, we need to bring in script to the XML document and then trigger it. There is no easy
way to do that in XML so we rely on (X)HTML tags such as form elements, as shown in this
next example.