Handle elements that have gone about poltergeist HOT 5 CLOSED

Actually, this is not quite true. Currently we are raising an ObsoleteNode error when the node is obsolete, and Capybara rescues this, causing has_no_selector? to return false.

The node's obsolete status is checked before we call invoke an operation on it. However, these two page.evaluate calls are separate. Therefore I think what is happening is that the element becomes obsolete in between its obsolete check and the actual call, causing an error. So we need to do it in one call.

from poltergeist.

Fixed in 3011b27.

from poltergeist.

Sorry to reopen this, i'm experiencing some random ObsoleteNodes now and then. If i understood it correctly, if i'm using a should_not have_content, poltergeist should be throwing this error and capybara would be responsible for rescuing that and having it to return false, right?

 Failure/Error: page.should_not have_content('foobar')
 Capybara::Poltergeist::ObsoleteNode:
   Capybara::Poltergeist::ObsoleteNode
 # (eval):2:in `has_no_content?'

When i run my specs, sometimes i get this kind of error, but normally after i run a couple of times, the tests are back to normal. Would this problem be related to this issue?

from poltergeist.

I'm not sure they're related. Could you please open a new issue so it doesn't get lost? Thanks

from poltergeist.

Ok! Done! #76

Thank you!

from poltergeist.