-
Notifications
You must be signed in to change notification settings - Fork 512
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
is_element_visible
: Check for StaleElementReferenceException
#903
Conversation
9a776f4
to
e399957
Compare
is_element_(not_)_visible
: Check for StaleElementReferenceException
is_element_(not_)_visible
: Check for StaleElementReferenceExceptionis_element_visible
: Check for StaleElementReferenceException
is_element_visible
: Check for StaleElementReferenceExceptionis_element_visible
: Check for StaleElementReferenceException
@jsfehler this can be reran now. This should fix the test |
Anything more you'd like to see for this? rationale:
my personal rationale is the same as when #396 did it's stale checks. just making sure the ones have it too |
e399957
to
dbaa101
Compare
Another friendly hello! :) And a rebase! 🙌 |
dbaa101
to
b8b87d7
Compare
Rebased again! |
This avoids the stale exception when checking for an element's visibility. Right now, we correctly do this in Anyone around? Can someone please take a look? |
@tony There's a few problems with this PR: |
b8b87d7
to
bb1fb2f
Compare
@jsfehler thank you for the response!
|
@tony Having re-read this PR, I'm not sure these changes will actually have any effect.
Do you have a particular scenario where |
@tony It looks like the call to Webdriver's
|
Closing this due to #1064 The new behaviour should be sufficient in this case. |
Robust, consistent handling for
is_element_visible_by_?
andis_element_not_visible_by_?
. We don't want either to blink at stale references.Prior art: consistent with #396, the function can continue to poll "freshly" without interruption by stale objects
Fixes #934