I just installed IE10 on my Windows 7, and I've noticed that, even if I'm glad that XMLs from AJAX requests are now compatible DOM documents, a rather basic function like document.evaluate
is still not supported.
What's worse is that, since those XMLs are not the custom Microsoft IXMLDocument
objects, the nodes don't support selectNodes
and selectSingleNode
anymore. In the end, it seems that IE10 does not support DOM Level 3 XPath or MSXML Xpath.
Seriously, Microsoft? Is there something I'm missing?
Sure, I can use querySelector
and querySelectorAll
, but I don't want to lose quite a bit of backward compatibility.
Otherwise, one can still request a MSXML document using this line
try {xhr.responseType = "msxml-document";} catch(e) {}
as stated here, but I think it would be nice to deal with, at last, a standard DOM document in IE too.
So, is there a way to use XPath in IE10 with standard DOM documents?
UPDATE 26/7/2013 IE11 isn't stable yet, but it still doesn't support document.evaluate
. If it won't support it in the stable release, I doubt it will ever support it. Needless to say this is ridicolous.
I get that you can use querySelector
/All
in DOM nodes, but it's not supported in IE9 and lower, which are still quite commonly used, and anyway XPath is more powerful than selectors.
Fortunately (if you can say that), you can still set xhr.responseType = "msxml-document"
. For a moment I feared you couldn't do that anymore...
UPDATE 23/11/2013 IE11 is stable now but, sadly, it doesn't support document.evaluate
. As heavy-weight XML documents are used less and less in web applications in favor of JSON or other light notation formats, this is becoming less of a problem, but still.
Setting the responseType
property still provides legacy XML documents, so nothing is lost I guess. I don't know if that will stay true for IE12, though.
UPDATE 15/8/2015 Sounds ridiculous right now, but Edge now supports document.evaluate
. Just when (almost) everything switched to JSON for data exchange. Well, better late than never, I guess.
Yes, there's still no XPath support in IE =/.
For me, the most reliable way to use document.evaluate
in every browser is, sadly, via a library.
It's called Wicked Good XPath and it's a recent Google-authored rewrite of the old good JavaScript-XPath library. I've been using Wicked Good XPath since the release and have been really comfortable with it (well, not as much as with a native XPath support, but still).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With