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 ie with watir-classic even though you specified chrome.
c = Watir::Browser.new :chrome
b.goto("cnn.com")
On Thursday, April 18, 2013 5:56:59 PM UTC-4, Chuck van der Linden wrote:
>
> On Thursday, April 18, 2013 3:46:02 AM UTC-7, Željko Filipin wrote:
>
>> On Thu, Apr 18, 2013 at 11:37 AM, <[email protected]> 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 watir-classic gems will be required, depending on your
>> platform and browser that you want to drive.
>>
>> Željko
>>
>
> Watir is now a wrapper around the other two. So that is why the code he
> is using works, and yes, he's actually using watir-webdriver when he does
> that. There's a .driver method you can use to select which driver (classic
> or webdriver) is actually used, and some logic that tried to guess smartly
> which one you want based on the OS and the browser type you specify.
>
> I've not played with it myself, I'm just using watir-webdriver, so I can't
> give you a lot of details.
>
--
--
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]
---
You received this message because you are subscribed to the Google Groups
"Watir General" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
