Changing from require 'watir-webdriver' to require 'watir' is not really a change. Because earlier watir was a meta gem, If you require 'watir' and if you just pass a parameter of chrome or firefox it automatically trigger the webdriver rather than watir-classic, the real change you have done here is, require 'watir' directly allow this line 'b=Watir::Browser.new' to trigger chrome browser.
To your second paragraph, I have read about that change in watir.github.io but I haven't implemented yet. And also my whole project lies in when_present whenever I need a return value 'self', If there is not, then wait_until_present. On Tuesday, November 15, 2016 at 9:45:49 PM UTC+5:30, Titus Fortner wrote: > > Watir 6.0 has been released! > > Implementation-wise, watir-classic has been deprecated, and > watir-webdriver has been renamed to watir (so just change `require > 'watir-webdriver'` to `require 'watir'` and bundle update) > > Watir has added a few new features; the biggest one has to do with how it > now defaults to waiting for new elements before taking actions. You should > be able to get rid of all references to `when_present` in your code. > > For more information: > > Watir 6.0 Blog announcement: http://watir.github.io/watir-6-0/ > Watir 6.0 FAQ: http://watir.github.io/watir-6-faq/ > > Thanks! > Titus > -- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com --- 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 watir-general+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
