Hi. I have the following xml in xml element
<commands><command oid="2" name="open" clientHandler="openHandler" /><command oid="27" name="padd" server="1"><argument quote="0" oid="26" name="Parent" autocomplete="1" /><argument quote="0" oid="28" name="State" autocomplete="1" /><argument quote="0" oid="43" name="Name" /></command><command oid="28" name="aadd" commandAC="1" server="1" /> .... </commands>
Some commands are with/without arguments.
the problem is that when I browse that in HTML I see that command w/oid 27 (padd) has one item in childNodes - arg w/oid 26; it has one child, argument w/oid 28, and it in turn has two children - next argument and next command.
Likewise when I do getElementsBytagName("argument") for command w/oid 27, I get all the subsequent argument tags regardless of real parents. Like, wtf? What about />? One thing to note is that both Ie and Firefox display this XML correctly when I copy-paste it into separate file; and IE also parses it correctly.
What's wriong with Firefox?
<commands><command oid="2" name="open" clientHandler="openHandler" /><command oid="27" name="padd" server="1"><argument quote="0" oid="26" name="Parent" autocomplete="1" /><argument quote="0" oid="28" name="State" autocomplete="1" /><argument quote="0" oid="43" name="Name" /></command><command oid="28" name="aadd" commandAC="1" server="1" /> .... </commands>
Some commands are with/without arguments.
the problem is that when I browse that in HTML I see that command w/oid 27 (padd) has one item in childNodes - arg w/oid 26; it has one child, argument w/oid 28, and it in turn has two children - next argument and next command.
Likewise when I do getElementsBytagName("argument") for command w/oid 27, I get all the subsequent argument tags regardless of real parents. Like, wtf? What about />? One thing to note is that both Ie and Firefox display this XML correctly when I copy-paste it into separate file; and IE also parses it correctly.
What's wriong with Firefox?