Compare Revisions

Introduction to using XPath in JavaScript

Revision 110874:

Revision 110874 by Celelibi on

Revision 110875:

Revision 110875 by Liorn on

Title:
Introduction to using XPath in JavaScript
Introduction to using XPath in JavaScript
Slug:
Introduction_to_using_XPath_in_JavaScript
Introduction_to_using_XPath_in_JavaScript
Tags:
DOM, XML, XSLT, Extensions, Add-ons, Transforming_XML_with_XSLT, XPath, "Web Development"
DOM, XML, XSLT, Extensions, Add-ons, Transforming_XML_with_XSLT, XPath, "Web Development"
Content:

Revision 110874
Revision 110875
n399      One possible workaround is to create a custom resolver thatn399      One possible workaround is to create a custom resolver that
> returns the correct default namespace (the Atom namespace in thi> returns the correct default namespace (the Atom namespace in thi
>s case). E.g.:>s case). Note that you still have to use some namespace prefix in
 > your XPath expression, so that the resolver function will be abl
 >e to change it to your required namespace. E.g.:
t405doc.evaluate('//entry', doc, resolver, XPathResult.ANY_TYPE, nullt405doc.evaluate('//myns:entry', doc, resolver, XPathResult.ANY_TYPE,
>)> null)

Back to History