This repository has been archived by the owner on Apr 30, 2022. It is now read-only.
Make lazy elements work with action builder, element handler and Selenium utilities #833
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
TroyWalshProf
requested review from
jason-edstrom,
jonreding2010,
billros and
JoshWencl
|
Fixes #832 |
jason-edstrom
approved these changes
Nov 4, 2021
|
Kudos, SonarCloud Quality Gate passed! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Some of the more complex Selenium interactions (such as Actions) require lower level element IDs.
Prior to this PR we gave Selenium no way to get a lazy element's element ID.
In this PR we address this gap by implementing the IWrapsElement interface.
This provide Selenium a standard way of getting a lazy element's element IDs.
*This is the same mechanism used by the EventFiringWebElement