chore: Skip staleness checks for subelement lookups#1063
Merged
Conversation
KazuCocoa
approved these changes
Oct 7, 2025
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 8, 2025
## [10.1.2](v10.1.1...v10.1.2) (2025-10-08) ### Miscellaneous Chores * Skip staleness checks for subelement lookups ([#1063](#1063)) ([ada7760](ada7760))
|
🎉 This PR is included in version 10.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
manabuaota
added a commit
to manabuaota/airtest-netease
that referenced
this pull request
Feb 14, 2026
## [10.1.2](appium/WebDriverAgent@v10.1.1...v10.1.2) (2025-10-08) ### Miscellaneous Chores * Skip staleness checks for subelement lookups ([#1063](appium/WebDriverAgent#1063)) ([ada7760](appium/WebDriverAgent@ada7760))
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It should make such requests faster for cases where accessibility hierarchy is big. See the discussion at appium/appium#21637 for more details