Nothing in the Ruby bindings have a hard coded 60 second timeout. Increasing the http_client timeout does in fact affect things. Selenium also now supports setting `open_timeout` and `read_timeout` independently.
If you think there is a problem with the code (Watir or Selenium), you are welcome to make a PR, or at least create an issue with a reproducible test case. On Friday, July 28, 2017 at 12:46:35 PM UTC-5, Raja gopalan wrote: > > I have reported this problem long time ago but you haven't given too much > attention to me. The problem is, the below code only applicable for > > b.goto '' not for every button click. So this is wrong! Button click waits > for 60 seconds to load but this 60 seconds is hard-coded inside selenium > ruby binding. it's not parameterized, So no matter whatever value you > change in client.timout in the below code it doesn't affect anything. > > > client = Selenium::WebDriver::Remote::Http::Default.new > client.timeout = 120 # seconds > driver = Selenium::WebDriver.for :remote, http_client: client > > > > On Friday, July 28, 2017 at 11:07:53 PM UTC+5:30, Titus Fortner wrote: >> >> Show us the code you are using and tell us what isn't working the way you >> expect. > > -- -- 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/d/optout.
