Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XPath is wrong when NodeFilter is used #156

bodewig opened this issue Jun 8, 2019 · 0 comments


Copy link

commented Jun 8, 2019

When using a NodeFilter the XPath for the Nodes (and their parents) in Comparison's details show the "reality" the difference engine has seen, not the one of the document itself. Elements that have been filtered away are not counted which may cause the indices of sibling elements to be smaller than they should be.

See also

@bodewig bodewig added bug core labels Jun 8, 2019

@bodewig bodewig added this to the 2.6.3 milestone Jun 8, 2019

@bodewig bodewig self-assigned this Jun 8, 2019

bodewig added a commit that referenced this issue Jun 8, 2019

@bodewig bodewig closed this in 8e94e6e Jun 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.