-
Notifications
You must be signed in to change notification settings - Fork 67
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
Node set predicate not working #25
Comments
I just test with 2.4.5 and I get the result that I expect.
|
It also appears to work with 2.5. |
appears to be broken in 2.7 as well |
Thanks for your report. |
naitoh
added a commit
to naitoh/rexml
that referenced
this issue
May 2, 2024
## Why? Fixed incorrect calculation of position in node set. See: ruby#25
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm upgrading Ruby from 2.4.5 to 2.6.5 and the rexml behavior seems to have changed. We actually had some xpaths that were wrong that were working with the previous version. However, in correcting them I'm seeing this issue:
I expect the following example to return just one node.
It returns two nodes though.
From my understanding placing an xpath subexpression in this
(...)[1]
should only return the first from the node set.-John
The text was updated successfully, but these errors were encountered: