This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
Kind test matches text() to both parsed and not parsed character nodes. #55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is needed because, although CDATA_SECTION_NODE type is deprecated,
popular browsers still use it when building DOM from xml files. (They ought to convert
incoming CDATA sections to TEXT_NODE but they don't.) At the same time the built in
evaluate function in Firefox, Chrome, Safari etc. return the right results by matching text()
to both types of node. wgxpath (and M.S. Edge) only match to TEXT_NODE type so
CDATA sections are treated as non-text.
Here is a jsfiddle that shows how wgxpath 1.3.0 gives unexpected results
https://jsfiddle.net/r73me5er/11/