One thing to note is that once you initialize one of the browsers you're
stuck with that driver that's chosen within the ruby session. Like if
you do something like this:
require 'watir'
# Starts with the watir-classic gem/driver
b = Watir::Browser.new :ie
b.goto(google.com)
# This will start
Hello Zeljko, thanks for your answer!
Regarding your answer: you said I have to use 'watir-webdriver'. But this
code *actually works*. I use it in production. I require 'watir, but
instantiate a :chrome browser.
So does that mean that watir-webdriver is implicitly imported?
Best,
g.
בתאריך
On Thursday, April 18, 2013 3:46:02 AM UTC-7, Željko Filipin wrote:
On Thu, Apr 18, 2013 at 11:37 AM, gu...@dna-7.com javascript: wrote:
So does that mean that watir-webdriver is implicitly imported?
As far as I know, yes. When you install/require watir gem, either
watir-webdriver or
Hello,
I would like to use *watir* rather than *watir-webdriver* since I want
watir's ability to wait until the next page loads after I submit a form in
my web application. *I've got both of them installed on the same machine.*
( Watir waits:
Hi g,
comments are inline.
On Wed, Apr 17, 2013 at 10:53 AM, gu...@dna-7.com wrote:
I would like to use *watir* rather than *watir-webdriver* since I want
watir's ability to wait until the next page loads after I submit a form in
my web application.
Watir project consists of several Ruby
