My suggestion would not to deal with that issue currently until watirspec specs are not passing. ~30% are still failing.
Jarmo On Mon, Jul 25, 2011 at 2:01 PM, Jari Bakken <[email protected]> wrote: > On Fri, Jul 15, 2011 at 11:11 PM, Bret Pettichord <[email protected]> > wrote: > > > > The big issue the remains open is the ownership and interface for > > Watir::Browser. Watir and Watir-Webdriver have conflicting versions of > this > > module/class. Watir's version (actually in common-watir) is pluggable to > use > > different implementations of watir-compatable drivers. Watir-WebDriver's > > assumes you are using webdriver for all browsers. What I would like to > see > > would be for Watir-Webdriver to rename its class and then update > > Watir::Browser to user Watir-Webdriver as the default implementation for > > Firefox and perhaps others. > > > > So would renaming Watir::Browser to Watir::WebDriver in > watir-webdriver solve this? > _______________________________________________ > Wtr-development mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-development >
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
