Comments (5)
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.
Related Issues (20)
- React event not triggered [help] HOT 2
- Capybara::Poltergeist::TimeoutError in some environments HOT 23
- ReferenceError: Can't find variable: Audio HOT 1
- React components not loading HOT 1
- Following jQuery line of code does not work in anything above v1.8.1 HOT 8
- Typo in keys method HOT 1
- Version of JS supported HOT 1
- Broken rails UJS loading when use arrow functions HOT 1
- Timeout occurs causing all following javascript tests to fail. HOT 3
- Capybara::Poltergeist::StatusFailError on 302 redirects with port numbers HOT 2
- Future of Poltergeist HOT 14
- Screenshot is not created HOT 1
- Authz request header missing HOT 5
- User agent does not persist across windows HOT 3
- Capybara::Poltergeist::TimeoutError when running CI tests HOT 7
- current_url returns empty string on about:blank HOT 3
- page.current_path always root HOT 2
- Possible make a method that check if JS Alert exist
- TypeError When dealing with link clicks via Capybara::Session HOT 2
- Capybara::Poltergeist::StatusFailError: failed to reach server (but manually I can connect perfectly) HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from poltergeist.