did you try upping the time out or using when_present to see if its a page loading issue? or do you already know that the page is completely loaded and expect it to fail
On Thu, Dec 13, 2012 at 2:48 PM, Abe Heward <[email protected]> wrote: > That'll be tough, unfortunately. The basic issue, though, is: > > 1) Target element (in my case it was a span being identified by its class) > does not exist on the page > 2) Use target_element.present? in a script > 3) Get a timeout error instead of false. > > I switched to using Chrome as my test browser for the time being and that > has at least gotten me unblocked for now--meaning it works fine in Chrome, > fails in Firefox 17. > > Hopefully someone will spot and fix the underlying error soon. > > Abe > > On Thursday, December 13, 2012 9:49:00 AM UTC-7, Željko Filipin wrote: > >> On Thu, Dec 13, 2012 at 4:09 PM, Abe Heward <[email protected]> wrote: >> >>> Sadly, an upgrade to the latest selenium-webdriver (2.27.2) hasn't >>> resolved this problem. :( >> >> >> Could you provide a minimal HTML and Ruby code to reproduce the problem? >> Or even better, link to the page with the problem? Or, do you get timeout >> errors everywhere? >> >> Željko >> > -- > Before posting, please read http://watir.com/support. In short: search > before you ask, be nice. > > [email protected] > http://groups.google.com/group/watir-general > [email protected] > -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
