Steven Parkes
Steven Parkes
I've always had a hard time keeping track of this. If you look at the capy google group, you'll find a few threads about it. I don't use it, so...
Thanks!
Cool. Let me know how it falls out. Depending on what the changes are, they might require driver changes.
It's probably related to env-js, some corner case env.js is handling (the JS frameworks do push env.js, often because they're trying to do some sort of feature detection, which means...
Any chance you could push a test case somewhere?
This is actually an env-js issue (which I also support). Looks like our xpath engine doesn't have everything that prototype wants. We are looking at another engine or might be...
Oh, and by the way, the "alert" not defined is a bug that I'll check in a fix soon, but it was just hiding the real issue.
Actually, the capybara driver needs access to xpath, so I'm pretty sure you'll need to save the reference and restore it, something like var saved_evaluate = window.evaluate; if (this.Envjs) {...
I think this is an xpath ordering assumption that is not guaranteed.
I was thinking it was actually clicking the wrong button. That's what that pull request talks about: there was a capy spec in that case that was failing for capy-envjs...