Watir 7.0.0.beta3 is now available on RubyGems. This update includes bug fixes and things that were intended for the last release for Capabilities but overlooked.
or in your Gemfile:
Unhandled Prompt Behavior
We documented in the capabilities guide the reason for why Watir is going to override the default behavior for Alert Handling. Except we forgot to implement it. It’s non-backward compatible, but we’re in beta. You must send a command to accept or dismiss the Alert if you are rescuing the exception. This will allow users to query whether an alert is present without changing the state of the system.
Selenium::WebDriver::Timeouts class has always converted script timeout, page load timeout,
and implicit wait timeouts from seconds (what the user enters) to milliseconds (what w3c spec expects).
When support for setting timeout values was added to the capabilities, it did not convert
from seconds to milliseconds. Watir now handles timeouts set in capabilities in a special way.
This is now deprecated:
Instead do this:
Note that Watir will now raise an exception if attempting to set an implicit wait because that conflicts with Watir’s automatic synchronization.
Watir was not properly handling valid vendor extension capabilities like
selenoid:options. This has been fixed.
See the Changelog for the complete history of updates.