fix: stale element refetching #15
Merged
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.
When an element is stale WebdriverIO will attempt to refetch it when a
command is run on it, such as a click.
Since WebElement JSONs are used directly to create the WebdriverIO
elements they do not have a selector which is used to attempt to refetch
them.
Custom locator strategies are able to add a selector to the resulting
element but still fail to refetch and cause problems with within for
unknown reasons. In future this may be a viable solution but not
currently.
Use SimmerJS to generate a unique selector for the element and send that
back from the browser, then use the selector as a string selector for $.
Using SimmerJS has the negative that much more text is being sent
between the browser and WebdriverIO.