Fix document fragment support as contextNode #143
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 PR is a fix for #142.
As mentioned in the issue, problem occurred when using ShadowRoot (document fragment) as the context node with absolute xpath.
Check in in PathExpr.applyLocationPath prevent it to fetch the ownerDocument as, in the case of ShadowRoot, it doesn't have acces to the nodes in the document-fragment.
Further in the code, document-fragment were forgotten as node MDN defines document-fragment as nodes.