Comments (11)
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
from wicked-good-xpath.
Issue 10 has been merged into this issue.
Original comment by [email protected]
on 10 Sep 2013 at 7:14
from wicked-good-xpath.
Issue 9 has been merged into this issue.
Original comment by [email protected]
on 10 Sep 2013 at 7:14
from wicked-good-xpath.
Issue 3 has been merged into this issue.
Original comment by [email protected]
on 10 Sep 2013 at 7:16
from wicked-good-xpath.
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
from wicked-good-xpath.
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
from wicked-good-xpath.
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
from wicked-good-xpath.
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
from wicked-good-xpath.
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
from wicked-good-xpath.
Issue 17 has been merged into this issue.
Original comment by [email protected]
on 14 Nov 2014 at 7:52
from wicked-good-xpath.
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
from wicked-good-xpath.
Related Issues (20)
- can i use it with xmldom on nodejs HOT 3
- Behavior differs from compiled vs. non-compiled library evaluating expression that returns different type than expected. HOT 4
- Allow installation on other nodes then document HOT 8
- Error: Object doesn't support property or method 'each' when using IE8 HOT 8
- Not evaluating expressions in IE. HOT 8
- XPathNSResolver HOT 3
- Namespace qualified wildcard step (ns:*) fails HOT 2
- Resolving a namespace with a different prefix than the one defined in the XML failed in IE9 and IE10 HOT 1
- A regression was introduced in r17: namespace prefixes failed to be evaluated in IE9 and IE10 HOT 2
- Doesn't work in IE11 HOT 5
- Non minified version HOT 2
- Complex expressions are not evaluated in IE11 HOT 2
- the local-name function uses prefixed names instead of local names HOT 7
- Fails to find <svg> child of <div> HOT 11
- Querying for //Person/Type returns 'string' on Chrome/FF and nothing on IE HOT 3
- XPath with multiple namespace fails in wgx but works in native Chrome/Firefox implementations HOT 2
- Support for XPath Axes HOT 5
- While evaluating xpath having element names with .(period) character fail with an error *Bad Token .*
- running tests HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wicked-good-xpath.