869626 - is_displayed() throwing a StaleElementException immediately after find_element()

Status: RESOLVED INVALID

(Remote Protocol :: Marionette, defect)

Description

[Bob Silverberg [:bsilverberg]]

Attachment: Test case that demonstrates the issue

Based on a discussion in IRC today, find_element() should always return a fresh element, i.e. if we call a method on an element immediately after getting a handle on it with find_element() that method should not throw a StaleElementException. One exception to this would be if a page transition happened between the call to find_element() and the element method, but this is highly unlikely.

We have a test case where we can consistently reproduce a StaleElementException when calling is_displayed() on an element immediately after finding it, and this seems to contradict the expected behaviour. I am attaching the test case so that it can be reproduced for debugging.

We do have a workaround for our test, which involves calling find_element(x).is_displayed() inside a wait_for_condition, and we're not entirely sure why it is working in that context and not when it's simply called on its own. As we have a workaround this is not a high priority, but it would be interesting to know why this is happening and if it is indicative of a Marionette bug.

Comment 1

[Bob Silverberg [:bsilverberg]]

I have done some more investigation and this seems to be a timing issue. Even though we are chaining find_element() and is_displayed(), the element seems to become stale *between* those two calls. I don't think this is a marionette issue.