Support for XMLDocument as well as document? about wicked-good-xpath

[GoogleCodeExporter]

For XML documents, IE provides native support for XPath through the selectNode 
and selectNodes methods.

It wouldn't be too hard for us to delegate to that method, so we will leave 
this open as a feature request.

Original comment by [email protected] on 10 Sep 2013 at 7:08

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Issue 10 has been merged into this issue.

Original comment by [email protected] on 10 Sep 2013 at 7:14

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by [email protected] on 10 Sep 2013 at 7:14

[GoogleCodeExporter]

Issue 3 has been merged into this issue.

Original comment by [email protected] on 10 Sep 2013 at 7:16

[GoogleCodeExporter]

For info: As you know there has been a substantial change in XML support by MS 
for IE over recent versions. The new HTTPrequest/XML implementation supports 
XML basic functions but has  big gaps when you try and use namespaces whereas 
the old native form does not.  You get this stupid (thanks yet again from 
Microsoft) position that they introduced the new XML object but it doesn't 
support everything most other browsers do according to international standards.

But the response actually does not address the question - for the question does 
not relate specifically to Internet Explorer. 

Original comment by [email protected] on 11 Sep 2013 at 7:33

[GoogleCodeExporter]

Does document.evaluate not function correctly on non-IE browsers? This library 
exists primarily because of IE's lack of native support for XPath, though it 
happens that there are a couple other use cases as well.

Original comment by [email protected] on 11 Sep 2013 at 3:18

[GoogleCodeExporter]

Yes

IE is a mess.

All browsers including recent IE have .evaluate method.  

Under new IE evaluate does not work with namespaces and so it is useless for 
searching via xpaths that have them and so we have to force IE to revert to 
native mode.

My specific point also is that there are several ways of getting an XML object, 
not just 

new DOMParser().  etc

And it would be really useful for your stuff to apply to all of them

For example the XMLhttprequest.responseXML property which we use very very 
heavily 

Hope this helps

Original comment by [email protected] on 12 Sep 2013 at 12:52

[GoogleCodeExporter]

I am using this lib as well for evaluating documents.

It is a rhino+env.js setup, where env.js misses a working xpath implementation

I am adding the evaluate method to document out of a DOMParser and it works as 
long as no namespaces are involved.

+1 for XML support.

Original comment by [email protected] on 11 Feb 2014 at 2:32

[GoogleCodeExporter]

to be more precise, namespace works but only if the xpath queries from the 
document node, not from a child node.

Original comment by [email protected] on 11 Feb 2014 at 3:33

[GoogleCodeExporter]

Issue 17 has been merged into this issue.

Original comment by [email protected] on 14 Nov 2014 at 7:52

[GoogleCodeExporter]

My use case for wgxp is to extend it with custom XPath functions and use if for 
XML Documents. Since native implementations cannot be extended, I have to use a 
JS library. 

If I understand the above correctly, this library will not have proper 
namespace support for XML Documents. 

Any plans to add this? Would it be a significant effort?

Original comment by [email protected] on 12 Mar 2015 at 5:20