fix: Support non-strict XPath queries #318
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KazuCocoa
approved these changes
Oct 28, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Oct 28, 2024
## [1.20.2](v1.20.1...v1.20.2) (2024-10-28) ### Bug Fixes * Support non-strict XPath queries ([#318](#318)) ([f596a61](f596a61))
|
🎉 This PR is included in version 1.20.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses https://discuss.appium.io/t/cannot-find-element-with-mac2/44959
In order to maintain the compatibility with the previously used libxml2 parser we need to "manually" patch incoming queries and make sure they always have the parent element type set. This is related to the fact NSXMLDocument's parser is strict and does not support the loose
//nodesyntax, but requires*/nodeor./nodeinstead