Re: [wtr-general] Re: Newer version has the new facility to interact with the table but it's not working

:) :) Ok that's great. On Aug 17, 2017 11:17 PM, "Titus Fortner" wrote: > It was a comment to someone else about another conversation. All of the > code examples in guides and blog posts on the Watir site should be > copy/pasted from code that's been actually verified

Re: [wtr-general] Re: This must be added into the recent Documentation in WATIR

and it will show each translation. > > > On Saturday, August 12, 2017 at 2:30:35 PM UTC-5, Raja gopalan wrote: >> >> *"Yes, I have written about my desire for users not to need to know XPath >>> before: http://watir.com/watir-6-2/#adjacent-element-location

[wtr-general] Re: This must be added into the recent Documentation in WATIR

aturday, August 12, 2017 at 11:12:54 AM UTC-5, Raja gopalan wrote: > >> >> Hi Titus, >> >> I read your recent document addition in WATIR site, it's looks great for >> a new comer. but, >> >> I believe one of the biggest area WATIR has the advan

[wtr-general] Re: This must be added into the recent Documentation in WATIR

atir.github.io/issues/101 > > I'm tentatively thinking about pulling in all of the html code we use in > our watirspecs onto the website, in order to have static pages to write > examples with. We could then copy and paste a lot of existing code in the > specs. > > >

[wtr-general] This must be added into the recent Documentation in WATIR

Hi Titus, I read your recent document addition in WATIR site, it's looks great for a new comer. but, I believe one of the biggest area WATIR has the advantage over Selenium is, It's capacity to eliminate the xpath conversation, but how and when it happened, it's not explained anywhere, I

Re: [wtr-general] Re: WATIR is not waiting for select_list to exist

obably not populated yet. Maybe its a generated > list. > Then wait for the option to be present > > browser.select_list(:id => 'theId').option(:value => > 'Ruby').wait_until_present > browser.select_list(:id => 'theId').option.wait_until_present > > On Thursday, Aug

Re: [wtr-general] Re: WATIR is not waiting for select_list to exist

usually works > sleep 30 > > A better method is to wait for it to be present > > b.select_list(:id => 'entry_1').when_present.select('Ruby') > or > b.select_list(:id => 'entry_1')..wait_until_present > > > > On Thursday, August 10, 2017 at 2:14:50 AM UTC-5, R

[wtr-general] Re: WATIR is not waiting for select_list to exist

Why it's not a bug? Take any html file, select_list part is acting in a same way, that is, it's not waiting for select_list to exist, for an example, consider the code below require 'watir' b.goto 'bit.ly/watir-webdriver-demo' b.element(id: 'entry_10').send_keys 'Hi' I made a mistake

[wtr-general] WATIR is not waiting for select_list to exist

If I write b.select_list(id: 'something').select("") default timeout is not applied here for a select_list, it immediately throws error if select_list doesn't exist but If I write the following code puts b.select_list(id: 'something').text #this would print the selected option value

Re: [wtr-general] Which browser is the best to work with watir (in long term)?

ike I said you can let it auto-update so > long as you make sure that the driver is auto-updated as well, which is > what the webdrivers gem does for you. > > > On Fri, Aug 4, 2017 at 1:29 PM, Raja gopalan <rajagopalanib...@gmail.com> > wrote: > >> Read what I write. Use

Re: [wtr-general] Which browser is the best to work with watir (in long term)?

Read what I write. Use legacy firefox driver,don't go for latest version of Firefox you might fall into the risk of using Geckodriver, Stopping the update of the Firefox is one of the easiest job in the world, so try to figure out how. On Aug 4, 2017 9:46 PM, "Damián M. González"

Re: [wtr-general] Which browser is the best to work with watir (in long term)?

Use Firefox and drive the firefox using Legacy firefox driver. You could 47.0.2 not above. Firefox driver has the visibility check if you use selenium directly to drive the browser, but If you use WATIR, then it directly handles that visibility check through program. On Fri, Aug 4, 2017 at 5:23

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

rowser`. > > On Thursday, August 3, 2017 at 2:28:55 AM UTC-5, Raja gopalan wrote: >> >> No, clearly not! >> >> >> I have written the below code >> >> puts '-' >> iframe=b.if

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

No, clearly not! I have written the below code puts '-' iframe=b.iframe(id: "mymodalerr") puts b.class b.alert.ok puts '-' Output - Watir::Browser

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

ll that isn't related to an alert > if an alert is displayed. > > > > On Monday, July 31, 2017 at 11:19:19 PM UTC-5, Raja gopalan wrote: >> >> Okay, this actually resolves the problem, Yes as you say, it's inside the >> frame and when I use as shown below >> >

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

u could have elements with the same id in multiple different > frames/browsing contexts. Watir requires you to explicitly specify which > one you want. > > > On Fri, Jul 28, 2017 at 12:42 PM, Raja gopalan <rajagopa...@gmail.com > > wrote: > >> But why this diffic

[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

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

Perhaps this could be of some problem? Error was thrown when I reach this line b.element(id: val).enabled? On Friday, July 28, 2017 at 12:00:05 PM UTC+5:30, Titus Fortner wrote: > > This is really hard to figure out from such little information > > put this at the very beginning of your co

[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

[wtr-general] Re: Trying to install new WATIR

I don't know why, it works fine now! I don't understand why this problem happens sometime. On Friday, June 23, 2017 at 2:11:27 AM UTC+5:30, Titus Fortner wrote: > > Looks like a rubygems issue. Let us know if you keep seeing it. -- -- Before posting, please read http://watir.com/support. In

[wtr-general] Trying to install new WATIR

I have recently noticed that new WATIR versions released, it's 6.4 now, but still I have been using WATIR version 6.2.1 So I decided to upgrade my WATIR but it's throwing following error C:\Users\Rajagopalan>gem install watir ERROR: Could not find a valid gem 'watir' (>= 0), here is why:

Re: [wtr-general] Help with how to access an element with this xpath

t.flash > @browser.element(:css => 'lwc-editIcon.ng-scope.ng-isolate-scope').click > > > > or > > @browser.element(:xpath, '//lwc-editIcon').wait_until_present.flash > > but these are not working. > > And I am not sure if we can access a custom tag like md-icon' >

Re: [wtr-general] Help with how to access an element with this xpath

b.element(xpath: "placeyourxpathhere").click On Jun 8, 2017 1:45 AM, "c w" wrote: > Hi, > > I need your help. > > Can one advise me how I can access the element that has the following > xpath into my angular app. > > /html/body[@class='lwc']/div[@class='lwc-app >

[wtr-general] Re: Watir 6.1.0 attch existing ie window using url/title

Hi WATIR 6.0 onwards watir lies on selenium, selenium doesn't have the facility of attaching the browser. But you move between the window of the browsers if browsers are opened by drivers(not manually). On Tuesday, May 16, 2017 at 1:26:16 AM UTC+5:30, sivam wrote: > > Hi, recently I have

Re: [wtr-general] Re: how to resize browser to different sizes or to maximize

e can you double check what ruby version you have. > > On Tue, May 2, 2017 at 10:00 AM, Raja gopalan <rajagopa...@gmail.com > > wrote: > >> >> hi, >> >> The below code is working for me in Firefox! >> >> @browser.driver.manage.window.maximize &g

Re: [wtr-general] Re: how to resize browser to different sizes or to maximize

you don't have use @browser.driver.manage.window.maximize because you are invoking the driver to write selenium code but watir giving you another syntax which will automatically invokes the above code @browser.window.maximize The definition of maximize includes the above code, you can see

Re: [wtr-general] Re: how to resize browser to different sizes or to maximize

hi, The below code is working for me in Firefox! @browser.driver.manage.window.maximize @browser.driver.manage.window.resize_to(900,900) require 'watir' is enough now, require 'watir-webdriver' is not necessary now. The recent watir is not a meta gem which doesn't choose betwen

[wtr-general] Re: how to resize browser to different sizes or to maximize

This is the wrong coding Right one is below @browser.driver.manage.window.maximize @browser.driver.manage.window.resize_to(900,900) On Tuesday, May 2, 2017 at 11:41:15 AM UTC+5:30, Paul Denize wrote: > > This should work > > @browser.driver.window.maximize >

[wtr-general] Page_load timout problem

I am having this error C:/Ruby23/lib/ruby/2.3.0/net/protocol.rb:158:in `rbuf_fill': Net::ReadTimeout (Net::ReadTimeout) from C:/Ruby23/lib/ruby/2.3.0/net/protocol.rb:136:in `readuntil' from C:/Ruby23/lib/ruby/2.3.0/net/protocol.rb:146:in `readline' from

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

Yes, WATIR manages extremely well! On Wednesday, March 29, 2017 at 7:13:36 AM UTC-7, Titus Fortner wrote: > > Yes, we discussed some of the peculiarities with matching strings and > regex a couple years ago: https://github.com/watir/watir/issues/342 > -- -- Before posting, please read

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

y to take a > longer look at it tonight. > > Titus > > On Tuesday, March 28, 2017 at 11:24:16 AM UTC-5, Raja gopalan wrote: >> >> hi, sorry, that was not done properly, here is the html file >> >> >> >> >> >> >> >> >&

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

> However, only the 2nd one, which is the one you want, is visible: > > b.links(:text, 'Recharge').map(&:visible?) > #=> [false, true, false, false, false, false, false, false] > > You get an exception in Watir because it is clicking on the first one, > which is hidde

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

es; > data-i18n="recharge" module-id="common">Recharge > > However, only the 2nd one, which is the one you want, is visible: > > b.links(:text, 'Recharge').map(&:visible?) > #=> [false, true, false, false, false, false, false, false] > > You get a

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

t does > look like Watir is grabbing a different, hidden element. I'll try to take a > longer look at it tonight. > > Titus > > On Tuesday, March 28, 2017 at 11:24:16 AM UTC-5, Raja gopalan wrote: >> >> hi, sorry, that was not done properly, here is the html file

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

t does > look like Watir is grabbing a different, hidden element. I'll try to take a > longer look at it tonight. > > Titus > > On Tuesday, March 28, 2017 at 11:24:16 AM UTC-5, Raja gopalan wrote: >> >> hi, sorry, that was not done properly, here is the html file

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

hi, sorry, that was not done properly, here is the html file Recharge On Monday, March 27, 2017 at 9:32:57 PM UTC-7, Titus Fortner wrote: > > This html doesn't have any links with text equal to "Recharge" > > > On Monday, March 27, 2017 at 11:13:

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

tBefore(ga, s); })(); On Monday, March 27, 2017 at 2:13:16 PM UTC-7, Titus Fortner wrote: > > I'd need to see the html to see why it works for one of the locator > strategies, but not the other. > > On Mon, Mar 27, 2017 at 1:21 PM, Raja gopalan <rajagopa...@gmail.com > > wrote: >

Re: [wtr-general] Exist method is needed while I use visible method, Can it be avoided?

pecification supported > means for clearing a field. > > (also of note, your code example is not platform independent) > > On Mon, Mar 27, 2017 at 1:35 PM, Raja gopalan <rajagopa...@gmail.com > > wrote: > >> Why do you want to execute such heavy function instead of pa

Re: [wtr-general] Exist method is needed while I use visible method, Can it be avoided?

ess of the industry. I get legacy apps and business or security > requirements, etc, etc, but this isn't 2002 any longer. > > You are more than welcome to avoid the clear call by using #send_keys > instead of #set > > > On Sunday, March 26, 2017 at 11:35:45 PM UTC-5, Raja gop

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

d to > see the underlying html. > > > On Sunday, March 26, 2017 at 11:38:52 PM UTC-5, Raja gopalan wrote: >> >> Link is clearly visible to click >> >> If I write >> >> @b.link(:text,'Recharge').click >> >> WATIR converts this code into >> >&

Re: [wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

at is not displayed? > > There are definitely ways that Watir can optimize its locator strategies, > but that part of the code is not trivial to dig into. As always, pull > requests are welcome. > > On Sun, Mar 26, 2017 at 12:18 PM, Raja gopalan <rajagopa...@gmail.com > > wrote:

Re: [wtr-general] Exist method is needed while I use visible method, Can it be avoided?

; > What we might be willing to do is to provide a command that will enter > text by JavaScript. I'm curious if that would solve your problem. > > On Sun, Mar 26, 2017 at 12:32 PM, Raja gopalan <rajagopa...@gmail.com > > wrote: > >> I completely agree, WATIR does i

Re: [wtr-general] Exist method is needed while I use visible method, Can it be avoided?

ending on what you are > trying to do. I have some ideas to increase performance in some situations, > but again, my focus is primarily on making it easy for people who don't > know all the details of their website's implementation to get consistent > results. > > Titus > &g

[wtr-general] Selenium clicks the line but WATIR doesn't click the same link, So there is a bug the way WATIR identifying the Link

I have written the following selenium code to click this link @driver.find_element(:link,'Recharge').click It successfully clicks the line I have written the same code in WATIR as shown below @b.link(:text,'Recharge').click but it throws element not present error I checked out how this

Re: [wtr-general] Exist method is needed while I use visible method, Can it be avoided?

nt to check if an element is both in the DOM and displayed on the > page. I rarely have occasion to use #visible? since #present? is almost > always the better option. > > https://github.com/watir/watir/blob/master/lib/watir/ > elements/element.rb#L392-L396 > > > > On Thursda

Re: [wtr-general] Problem with b.alert.ok

you can see in the logs you provided) it also > closes the alert, which is why it wasn't there when your code polled for it. > > Titus > > > On Wed, Mar 22, 2017 at 11:57 PM, Raja gopalan <rajagopa...@gmail.com > > wrote: > >> Thank you Titus, but you haven't e

Re: [wtr-general] Exist method is needed while I use visible method, Can it be avoided?

atir once you get more used to all of the > dom methods it provides. it wraps a much more sophisticated api around the > webdriver stuff. > > > > -- > *From:* Raja gopalan <rajagopalanib...@gmail.com> > *To:* Watir General <watir-ge

Re: [wtr-general] Exist method is needed while I use visible method, Can it be avoided?

Titus, I stongly believe checking enabled? present? writable? methods are unnecessary calls by WATIR because we know what kind of field we are going to interact so these calls to every element slows down the process So what I did was, I have CALLED the driver out of WATIR and started writing

Re: [wtr-general] Exist method is needed while I use visible method, Can it be avoided?

? instead > > > ------ > *From:* Raja gopalan <rajagopalanib...@gmail.com> > *To:* watir-general@googlegroups.com > *Sent:* Thursday, March 23, 2017 9:52 AM > *Subject:* [wtr-general] Exist method is needed while I use visible > method, Can it be avoided? > > I find

Re: [wtr-general] Exist method is needed while I use visible method, Can it be avoided?

? instead > > > ------ > *From:* Raja gopalan <rajagopalanib...@gmail.com> > *To:* watir-general@googlegroups.com > *Sent:* Thursday, March 23, 2017 9:52 AM > *Subject:* [wtr-general] Exist method is needed while I use visible > method, Can it be avoided? > > I find

Re: [wtr-general] Problem with b.alert.ok

wasn't there when your code polled for it. > > Titus > > > On Wed, Mar 22, 2017 at 11:57 PM, Raja gopalan <rajagopalanib...@gmail.com > > wrote: > >> Thank you Titus, but you haven't explained me why inspect method closes >> the alert? What's the reason? >>

Re: [wtr-general] Problem with b.alert.ok

is a bug, but thankfully an easy fix. > > https://github.com/watir/watir/pull/543/commits/1ef85710 > > Expect this to be released in 6.2.1 later this week. > > Thanks for reporting it! (and being persistent with answering my questions) > > Titus > > > On Wednesday, March 22, 20

Re: [wtr-general] Problem with b.alert.ok

tocol). > > What is your code between the element click and the alert click? > > > > > On Tuesday, March 21, 2017 at 3:43:31 PM UTC-5, Raja gopalan wrote: >> >> Yes it's not happening in Chrome, it works fine there. >> >> What you asked >> >> 2017-03-22

Re: [wtr-general] Problem with b.alert.ok

latest version of Watir, you can place this above the > code of concern: `Selenium::WebDriver.logger.level = :info` and paste the > output. > > Thanks > > On Tuesday, March 21, 2017 at 2:29:59 PM UTC-5, Raja gopalan wrote: >> >> If I remove Inspect from that line it works v

Re: [wtr-general] Problem with b.alert.ok

If I remove Inspect from that line it works very fine that means that line crosses by leaving alert open so that wait unit passes. By the way what is the rest of the info? On Mar 22, 2017 12:56 AM, "Titus Fortner" wrote: > Interesting. I need the rest of the information

Re: [wtr-general] Problem with b.alert.ok

this above the alert code: `Selenium::WebDriver.logger.level = :info` and then reply with the output. On Tue, Mar 21, 2017 at 12:47 PM, Raja gopalan <rajagopalanib...@gmail.com> wrote: > I have written the following code to handle alert > > b.alert.ok > > Please look at the be

[wtr-general] Problem with b.alert.ok

I have written the following code to handle alert b.alert.ok Please look at the below code(bottom), I went through debug, when it reaches to message ||= "waiting for true condition on #{inspect}" it automatically closes the alert so when it reaches to next line, that is Wait.until(timeout:

Re: [wtr-general] Re: Error while Selecting select_list by Value

t; Inputs can be disabled. > For example, https://www.w3schools.com/tags/att_option_disabled.asp > https://www.w3schools.com/tags/att_select_disabled.asp > > > > > On Friday, March 17, 2017 at 10:22:05 AM UTC-5, Raja gopalan wrote: >> >> Ok another problem I see here is aft

Re: [wtr-general] Re: Error while Selecting select_list by Value

orks manually? > > Inputs can be disabled. > For example, https://www.w3schools.com/tags/att_option_disabled.asp > https://www.w3schools.com/tags/att_select_disabled.asp > > > > > On Friday, March 17, 2017 at 10:22:05 AM UTC-5, Raja gopalan wrote: >> >> Ok another

Re: [wtr-general] Re: Error while Selecting select_list by Value

dles > would likely change. > Good luck. Let us know your success. > > On Friday, March 17, 2017 at 10:13:08 AM UTC-5, Raja gopalan wrote: >> >> It refreshes the page after the selection, might that be the reason? >> >> Note : selection is successfully hap

Re: [wtr-general] Re: Error while Selecting select_list by Value

select causing a page navigation after selecting the option? >> >> On Friday, March 17, 2017 at 8:44:35 AM UTC-5, Raja gopalan wrote: >>> >>> Actually the option is selected successfully, but immediately after the >>> selection, this error was thrown and

Re: [wtr-general] Re: Error while Selecting select_list by Value

No but it refreshes the page . On Mar 17, 2017 8:08 PM, "Lucas Tierney" <lucast1...@gmail.com> wrote: > Is the select causing a page navigation after selecting the option? > > On Friday, March 17, 2017 at 8:44:35 AM UTC-5, Raja gopalan wrote: >> >> Actuall

Re: [wtr-general] Re: Error while Selecting select_list by Value

attached to a parent object which has > refreshed. ( a div, a table, an element, who knows) > This is based on the assumption: > b.select_list(:id,'PolicyTypeANDL').select_value > '225' > where b is just the gross browser object. > > > > On Wednesday, March 15, 201

Re: [wtr-general] Error while Selecting select_list by Value

I am using legacy Firefox driver Because as I told you earlier Geckodriver is not choosing the select list option To the above problem the option is successfully selected but after the selection this error was thrown. On Mar 15, 2017 5:58 PM, "Titus Fortner" wrote: >

Re: [wtr-general] Re: Error while Selecting select_list by Value

No, this error happens once out of ten times may be On Mar 15, 2017 10:13 PM, "Arik Jones" <tny...@gmail.com> wrote: > Are you loading any firefox plugins that change the state of the DOM? > > On Wednesday, March 15, 2017 at 3:24:23 AM UTC-4, Raja gopalan wrote: >

Re: [wtr-general] Re: Error while Selecting select_list by Value

sday, March 15, 2017 at 2:24:23 AM UTC-5, Raja gopalan wrote: >> >> I have written the code to select the select list >> >> b.select_list(:id,'PolicyTypeANDL').select_value '225' >> >> It's working sometime and it's throwing error some time, >> >>

[wtr-general] Error while Selecting select_list by Value

I have written the code to select the select list b.select_list(:id,'PolicyTypeANDL').select_value '225' It's working sometime and it's throwing error some time, Error is, Uncaught exception: [JavaScript Error: "can't access dead object" {file:

Re: [wtr-general] I find a bug in automating firefox with geckodriver

Ok thank you! I was not aware that it's a known issue. On Mar 12, 2017 12:33 AM, "Titus Fortner" wrote: > This is a known issue with geckodriver. The w3c spec calls for being able > to specify one of three levels. The default is supposed to wait for > document ready

[wtr-general] I find a bug in automating firefox with geckodriver

When we click a button to navigate the next page, it doesn't wait for next page to appear, it moves to execute the next command while page still loads but when we use ' legacy Firefox driver' it waits for next page to complete load. Selenium also promises that it locks other operation if button

Re: [wtr-general] Is it possible to automate Firefox browser lower than 45 version using WATIR 6.2?

r us to be able to diagnose your > issue. What code are you using on what html? Often it is useful to check if > your code works with chrome. > > > On Mar 6, 2017 2:33 AM, "Raja gopalan" <rajagopa...@gmail.com > > wrote: > > Yeah it works now, the code I have writ

Re: [wtr-general] Is it possible to automate Firefox browser lower than 45 version using WATIR 6.2?

: false) b=Watir::Browser.new :firefox, desired_capabilities: caps On Monday, 6 March 2017 13:08:14 UTC+5:30, Titus Fortner wrote: > > You need to pass in a Capabilities object with marionette: false for > Firefox less than 48. > > On Mar 6, 2017 1:19 AM, "Raja gopalan&quo

[wtr-general] Is it possible to automate Firefox browser lower than 45 version using WATIR 6.2?

I am trying to automate the firefox browser which is lower than 45 that is 38, but it's throwing this error C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.2.1/lib/selenium/webdriver/remote/response.rb:69:in `assert_ok': Missing 'marionetteProtocol' field in handshake

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

> > browser.text_field.send_keys "hello", [:control, "a"], :backspace > > See: > https://watirmelon.blog/2011/07/19/sending-special-keys-to-watir-webdriver/ > > http://www.rubydoc.info/github/watir/watir-classic/Watir%2FElement%3Asend_keys > > >

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

tir/watir-classic/Watir%2FElement%3Asend_keys > > > > On Friday, February 17, 2017 at 5:36:11 AM UTC-6, Raja gopalan wrote: >> >> Hi Titus, >> >> Sorry for late reply! Your code which has been given in Stackoverflow is >> a good catch but you are missing t

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

t; browser.text_field.send_keys "hello", [:control, "a"], :backspace >> >> See: >> https://watirmelon.blog/2011/07/19/sending-special-keys-to-watir-webdriver/ >> >> http://www.rubydoc.info/github/watir/watir-classic/Watir%2FElement%3Asend_keys >&g

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

llo", [:control, "a"], :backspace >> >> See: >> https://watirmelon.blog/2011/07/19/sending-special-keys-to-watir-webdriver/ >> >> http://www.rubydoc.info/github/watir/watir-classic/Watir%2FElement%3Asend_keys >> >> >> >&

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

ps bad JS validation or field validation. > You can always put a static sleep as a work-around. Not elegant. > Change the sets to send keys and see if the behaviour alters. > > > On Monday, February 13, 2017 at 12:10:45 PM UTC-6, Raja gopalan wrote: >> >> Hi, I have re

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

field validation. >> You can always put a static sleep as a work-around. Not elegant. >> Change the sets to send keys and see if the behaviour alters. >> >> >> On Monday, February 13, 2017 at 12:10:45 PM UTC-6, Raja gopalan wrote: >>> >>> Hi, I

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

>> bug. Perhaps bad JS validation or field validation. >> You can always put a static sleep as a work-around. Not elegant. >> Change the sets to send keys and see if the behaviour alters. >> >> >> On Monday, February 13, 2017 at 12:10:45 PM UTC-6, Raja gopalan wr

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

> On Monday, February 13, 2017 at 12:01:55 PM UTC-6, Raja gopalan wrote: >> >> My problem is after setting the value. Page is getting refreshed after >> setting the value. >> >> On Monday, February 13, 2017 at 9:09:18 AM UTC+5:30, Joe Fl wrote: >>> >

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

er the field is set but if you >> need to wait for the text field you can use wait_until_present or .present?. >> >> Joe >> >> >> On Feb 11, 2017 10:21 AM, "Raja gopalan" <rajagopa...@gmail.com >> > wrote: >> >> The

Re: [wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

eld you can use wait_until_present or .present?. > > Joe > > On Feb 11, 2017 10:21 AM, "Raja gopalan" <rajagopa...@gmail.com > > wrote: > > There are certain kind of a text_field which I am automating, when I place > the value there like > > b.text_fie

[wtr-general] Placing the value inside the text field loads the entire page, So Is there any function which will wait for the page load?

There are certain kind of a text_field which I am automating, when I place the value there like b.text_field(:id,'something').set 'hi' It refresh the entire page or it reloads the page, but the above code only wait until element present and place the value inside the text field but it

[wtr-general] Re: angular login

If you use browser=Selenium::WebDriver.new :chrome Then you need to use browser. find_element(:id,'email').send_keys "('em...@email.com')" If you use browser=Watir::Browser.new browser.text_field(:id,'email').set "('em...@email.com')" On Friday, February 3, 2017 at 11:49:53 PM UTC+5:30,

Re: [wtr-general] Is there any way I can adjust the predefined waiting time in WATIR 6.1.0

wait. > If you want to increase it for a specific element interaction: > > `b.button.wait_until(timeout: 45, &:present?).click` > > On Fri, Feb 3, 2017 at 11:22 AM, Raja gopalan <rajagopa...@gmail.com > > wrote: > >> This code >> >> b.button(:value,'Next').

[wtr-general] Is there any way I can adjust the predefined waiting time in WATIR 6.1.0

This code b.button(:value,'Next').click > has the implicit waiting time Is there any way I can increase the waiting time? where do I have to set it? -- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com

Re: [wtr-general] Re: invalid element state: Element is not currently interactable and may not be manipulated(classic works fine, but webdriver is throwing this error)

de a link, create one using > jsfiddle.net > > On Sat, Dec 17, 2016 at 3:18 PM, Raja gopalan <rajagopa...@gmail.com > > wrote: > >> Okay, what do you want? Coding part of that text_field? >> >> On Sunday, December 18, 2016 at 2:35:51 AM UTC+5:30, Titus Fortner

Re: [wtr-general] Re: invalid element state: Element is not currently interactable and may not be manipulated(classic works fine, but webdriver is throwing this error)

you any more. > > On Sat, Dec 17, 2016 at 3:02 PM, Raja gopalan <rajagopa...@gmail.com > > wrote: > >> Yes, I have tried with watir-scroll as well, but it also throws the >> error. >> >> >> On Sunday, December 18, 2016 at 2:30:31 AM UTC+5:30

[wtr-general] Re: invalid element state: Element is not currently interactable and may not be manipulated(classic works fine, but webdriver is throwing this error)

eding to set a debug point. > > Titus > > On Saturday, December 17, 2016 at 2:44:24 PM UTC-6, Raja gopalan wrote: >> >> Yes, I know classic is only for IE, But when I used watir-webdriverfor >> both IE and Chrome, both are throwing this same error. It's a lengthy

[wtr-general] Re: invalid element state: Element is not currently interactable and may not be manipulated(classic works fine, but webdriver is throwing this error)

oducible test case it would be > difficult to diagnose further, but you are likely trying to do something > differently than how a user to the site would be doing it. > > Titus > > On Saturday, December 17, 2016 at 1:57:36 AM UTC-6, Raja gopalan wrote: >> >> I am runnin

[wtr-general] invalid element state: Element is not currently interactable and may not be manipulated(classic works fine, but webdriver is throwing this error)

I am running the same code in Watir-classic and WATIR 6.0.2 WATIR-CLASSIC runs without any problem, but WATIR 6.0.2 throwing this error > > [12:39:18] [ERROR] : invalid element state: Element is not currently > interactable and may not be manipulated > (Session info: chrome=55.0.2883.87) >

Re: [wtr-general] How to open the new tab in chrome using ruby watir in rubymine

Lucas, Thank you, it works fine. On Tuesday, December 13, 2016 at 8:47:25 PM UTC+5:30, Lucas Tierney wrote: > > You need to have 'http://' in front of 'www.yahoo.com' (look at how Titus > did it) > > On Tuesday, December 13, 2016 at 8:12:40 AM UTC-6, Raja gopalan wrote: >>

Re: [wtr-general] How to open the new tab in chrome using ruby watir in rubymine

It's opening new window but it's loading wrong url in the second window, for an example, I have written the following code require 'watir' > b=Watir::Browser.new :chrome > b.goto 'www.google.com' > b.execute_script('window.open("www.yahoo.com")') > > gets but it's loading the given below url,

[wtr-general] Re: I want to disable this implicit 'when_present'

Yes, it works, thanks. On Monday, December 5, 2016 at 7:24:38 PM UTC+5:30, Lucas Tierney wrote: > > You should be able to disable the when_present waiting before actions by > setting Watir.relaxed_locate = false > > On Monday, December 5, 2016 at 7:21:35 AM UTC-6, Raja gopalan w

[wtr-general] I want to disable this implicit 'when_present'

How do I do that? I want to disable this implicit when_present, how do I do that? It's waiting in some places for a long time which I could check in my log so easily. -- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice.

[wtr-general] Re: Couldn't start the mozilla using WATIR 6.0.2

ers gem to have it automatically > manage your drivers for you: > https://github.com/titusfortner/webdrivers#usage > > > > On Monday, November 28, 2016 at 2:32:10 AM UTC-8, Raja gopalan wrote: >> >> geckodriver >> >> On Monday, November 28, 2016 at 3:22:38 PM U

[wtr-general] Re: Couldn't start the mozilla using WATIR 6.0.2

geckodriver On Monday, November 28, 2016 at 3:22:38 PM UTC+5:30, gary wrote: > > is it the latest geckodriver and the latest v. of firefox? > > On Friday, 25 November 2016 16:28:43 UTC, Raja gopalan wrote: >> >> I have written the following code >>> &g

Re: [wtr-general] browser closing on error

Hi Titus, If it's internet explorer, it's not closing the browser, if it's chrome, then it's not closing the browser. Can you make this as a default one as it's in Internet Explorer? On Friday, November 25, 2016 at 6:18:47 AM UTC+5:30, Titus Fortner wrote: > > Oh, this could be due to a

Re: [wtr-general] browser closing on error

Hi Titus, I was sorry about the last reply, I noticed that it's closing after long time. It's fine. Thanks. On Friday, November 25, 2016 at 6:18:47 AM UTC+5:30, Titus Fortner wrote: > > Oh, this could be due to a change we made in selenium a few months back. > If you pass in detach: true to

  1   2   >