Re: [wtr-general] Selenium Code is working but WATIR code fails to produce the result

Working with iframes is approached differently in selenium & Watir. In Selenium you are responsible for explicitly switching into and out of the context you want: driver.switch_to.frame('iframe1') driver.find_element(id: 'element_inside_frame').click driver.switch_to.default_content

[wtr-general] Re: Watir change Internal time

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

[wtr-general] Re: Watir change Internal time

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

Re: [wtr-general] Selenium Code is working but WATIR code fails to produce the result

But why this difficulty while I use in WATIR? Selenium is allowing me to access without any these kind of trouble. WATIR should eases that the selenium coding, but here it makes it difficult. On Friday, July 28, 2017 at 8:20:51 PM UTC+5:30, Titus Fortner wrote: > > Watir should now only send

[wtr-general] Watir change Internal time

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. watir-general@googlegroups.com http://groups.google.com/group/watir-general

[wtr-general] Watir change Internal time

Hi, Recently I faced an problem which caused timeout issue Net::ReadTimeout (Net::ReadTimeout) And I found some related infomation in selenium which refer to this document https://github.com/SeleniumHQ/selenium/wiki/Ruby-Bindings Internal timeouts Internally, WebDriver uses HTTP to

Re: [wtr-general] Selenium Code is working but WATIR code fails to produce the result

Watir should now only send the null value to the frame endpoint if the element in question is inside an iframe. So this could make sense. You need to include the iframe definition as a parent object whenever defining elements inside of it. -- -- Before posting, please read

Re: [wtr-general] Selenium Code is working but WATIR code fails to produce the result

Okay, when I execute this line b.element(id: val).present? It returns this output 2017-07-28 12:17:02 INFO Selenium -> POST session/693a490267a80a9ec48e9cd860162b22/frame 2017-07-28 12:17:02 INFO Selenium>>> http://127.0.0.1:9515/session/693a490267a80a9ec48e9cd860162b22/frame |

Re: [wtr-general] Selenium Code is working but WATIR code fails to produce the result

This is really hard to figure out from such little information put this at the very beginning of your code: `Selenium::WebDriver.logger.level = :info` Then instead of clicking the element do: ``` val = 'B10_1_4' b.element(id: val).present? b.element(id: val).enabled? b.driver.find_element(id:

[wtr-general] Selenium Code is working but WATIR code fails to produce the result

Hi Titus, down votefavorite In my application, I am writing the following code b.element(id: 'B10_1_4').click It's not working and it's throwing the unable to locate the