js parsing xml string and xml document implementation principle and code (for ie and firefox)_javascript skills

We have parsed XML documents and XML strings for IE and Firefox respectively. All codes are commented out. If you want to see some functions, just remove the comments.

As for parsing xml in an ajax environment, the principle is actually the same, except that if it is placed in ajax, the returned xml still needs to be parsed.

Copy code The code is as follows:

head>

Use js to parse xml documents and xml strings


<script> <BR>//Parse xml document//////////////////////////////////////////////////// ///// <BR>var xmlDoc=null; <BR>//Support IE browser <BR>if(window.ActiveXObject){ <BR>xmlDoc=new ActiveXObject("Microsoft.XMLDOM"); <BR> } <BR>//Support Mozilla browser<BR>else if(document.implementation && document.implementation.createDocument){ <BR>xmlDoc = document.implementation.createDocument('','',null); <BR> } <BR>else{ <BR>alert("here"); <BR>} <BR>if(xmlDoc!=null){ <BR>xmlDoc.async = false; <BR>xmlDoc.load("house. xml"); <BR>} <BR>//IE and Firefox not only have different parsers, but also different parsing processes. As follows; <BR>//ie parse xml document<BR>//alert(xmlDoc.getElementsByTagName("address")[0].childNodes[0].childNodes[0].childNodes[0].nodeValue);// Pop up 1.5 million<BR>//alert(xmlDoc.getElementsByTagName("address")[0].childNodes[0].childNodes[1].childNodes[0].nodeValue);//pop up one bedroom and three bedrooms<BR> //Traverse and parse childNodes[1] <BR>//alert(xmlDoc.childNodes[1].childNodes[1].childNodes[0].childNodes[0].nodeValue);//pop up 2 million <BR> //alert(xmlDoc.childNodes[1].childNodes[0].childNodes[0].childNodes[0].nodeValue); //1.5 million pops up<BR>//alert(xmlDoc.childNodes[1].childNodes[ 0].childNodes[1].childNodes[0].nodeValue);//Pop up one room and three bedrooms<BR>//You can also use item(i) to traverse<BR>//var nodes=xmlDoc.documentElement.childNodes ; <BR>//alert(nodes.item(0).childNodes.item(0).childNodes.item(0).text); //1.5 million pops up<BR>//alert(nodes.item(0) .childNodes.item(1).childNodes.item(0).text); //Pop up one room and three bedrooms<BR>//Firefox parses xml document<BR>//Firefox and IE parse xml for different nodes Use textContent for the value. <BR>//And it will add "n" line breaks before and after some hierarchical child nodes. (I don’t know why. It looks like this when debugging with firebug, so it is best to test the code you have written. It will not be correct in another environment) <BR>//In other words, the first node is "n", and the first node is "n". 2 nodes are the real first node. <BR>//The third node is "n", and the fourth node is the real second node. <BR>//Get and parse childNodes[0] layer by layer <BR>//alert(xmlDoc.childNodes[0].childNodes[1].childNodes[1].textContent);//pop up 1.5 million<BR>// alert(xmlDoc.childNodes[0].childNodes[1].childNodes[3].textContent);//Pop up a three-bedroom apartment<BR>//Get the node name resolution directly getElementsByTagName("address") <BR>// alert(xmlDoc.getElementsByTagName("address")[0].textContent);//Pop up 1.5 million for one bedroom and three bedrooms for 2 million and 3 million <BR>//alert(xmlDoc.getElementsByTagName("address")[0].childNodes [1].textContent);//Pop up 1.5 million for one room and three bedrooms<BR>//alert(xmlDoc.getElementsByTagName("address")[0].childNodes[1].childNodes[1].textContent);// Pop up 1.5 million<BR>//alert(xmlDoc.getElementsByTagName("address")[0].childNodes[1].childNodes[3].textContent);//Pop up one room and three bedrooms<BR>//alert(xmlDoc .getElementsByTagName("address")[0].childNodes[3].textContent);//pop up 2 million <BR>//Firefox can also use the item(1) function to traverse. Note that some hierarchical nodes are also added before and after Node "n". <BR>//The first node is item(1), the second node is item(3), and the third node is item(5) <BR>//item(1) function traversal analysis<BR>/ /var nodes=xmlDoc.documentElement.childNodes; <BR>//alert(nodes.item(1).textContent); //pop up 1.5 million one-bedroom, three-bedroom <BR>//alert(nodes.item(1). childNodes.item(1).textContent); //1.5 million pops up<BR>//alert(nodes.item(1).childNodes.item(3).textContent); //One bedroom and three bedrooms<BR>// Parse xml string ////////////////////////////////////////////////// //////////////////////////// <BR>var str="<car>" <BR>"<brand><price&gt ;500,000<pattern>A6" <BR>"<brand><price>650,000<pattern>A8&gt ;" <BR>"<brand><price>170,000" <BR>""; <BR>//Cross-browse The parsers used by IE and Firefox to parse xml are different.<BR>var xmlStrDoc=null; <BR>if (window.DOMParser){// Mozilla Explorer <BR>parser=new DOMParser(); <BR>xmlStrDoc=parser.parseFromString(str,"text/xml"); <BR>}else{// Internet Explorer <BR>xmlStrDoc=new ActiveXObject("Microsoft.XMLDOM"); <BR>xmlStrDoc.async="false"; <BR>xmlStrDoc.loadXML(str); <BR>} <BR>//ie parse xml string<BR>//alert(xmlStrDoc.getElementsByTagName("car")[0].childNodes[0].childNodes[0].childNodes[0].nodeValue);//pop up 500,000<BR>//alert(xmlStrDoc.getElementsByTagName("car")[0].childNodes[0].childNodes[1].childNodes[0].nodeValue);//Pop up A6 <BR>//Alright Use item(i) to traverse <BR>//var strNodes=xmlStrDoc.documentElement.childNodes; <BR>//alert(strNodes.item(0).childNodes.item(0).childNodes.item(0).text ); //pop up 500,000 <BR>//alert(strNodes.item(0).childNodes.item(1).childNodes.item(0).text); //pop up A6 <BR>//Firefox parses xml String <BR>//Firefox and IE use textContent to parse the values ​​of different nodes in xml. <BR>//And it will add "n" line breaks before and after some hierarchical child nodes. <BR>//In other words, the first node is "n", and the second node is the real first node. <BR>//The third node is "n", and the fourth node is the real second node. <BR>//alert(xmlStrDoc.childNodes[0].childNodes[1].textContent);//pop up 650,000 A8 <BR>//alert(xmlStrDoc.childNodes[0].childNodes[1].childNodes[1 ].textContent);//A8 <BR>//alert(xmlStrDoc.childNodes[0].childNodes[1].childNodes[0].textContent);//pop up 650,000<BR>//Firefox can also use item (1) Function traversal, note that there are also nodes "n" added before and after some hierarchical nodes. <BR>//The first node is item(1), the second node is item(3), and the third node is item(5) <BR>//var nodes=xmlStrDoc.documentElement.childNodes; <BR>//alert(nodes.item(1).textContent); //pop up 650,000 A8 <BR>//alert(nodes.item(1).childNodes.item(0).textContent); //pop up 650,000 A8 <BR>//alert(nodes.item(1).childNodes.item(1).textContent); //Pop up A8 <BR></script>

where xml is for each node The level is the most annoying problem. You can only try it again and again. As long as the correct one comes out,
you can easily determine the hierarchical relationship of the nodes, or debug it.

I feel that json is better to read and understand in this regard. This parsing is too laborious

Copy code The code is as follows:

1.5 million
One bedroom and three bedrooms


2 million


2.3 million