[wtr-general] Re: click_no_wait again
Jarmo,
I am pasting my code again here for your reference:
$b = Watir::IE.attach(:url, "myurl")
sleep(2)
btn = $b.button(:id, "btnClear")
$DEBUG = true
btn.click_no_wait()
$DEBUG=false
I created my first browser object by an attach as in the first
statement above. I didn't use any other attach statements in MY code.
However, when I added the $DEBUG=true statement, the error message it
output had another attach statement in it. Please refer my first
email. This is coming from the implementation of click_no_wait
function. click_no_wait seems to use attach internally to connect to
the window that is pop opening. Clarification: I didn't do it!
Until I had the Watir::IE.attach in my code to attach to my
page("myurl"), my code didn't work.
I had to change the code as:
$b=Watir::Browser.new
$b.goto("myurl")
:
:
And, everything started working fine.
I hope it makes some sense to you now. If not, god save me!! :) I
have called it quits.
Thanks
Babitha
I hope
On Jun 5, 7:04 am, Jarmo Pertman wrote:
> I still don't understand it all exactly. You had a browser object and
> ended up on the page where was a button, which created a javascript
> dialog upon clicking and then you used #attach for some reason and it
> didn't work? #attach should work, i don't see any reasons why it
> shouldn't.
>
> But regarding Javascript popups i'd avoid them altogether by
> overriding appropriate javascript function at correct place. You can
> read more about that from "Simplest way to stop JavaScript Pop Ups
> from showing when running your Watir tests"
> athttp://wiki.openqa.org/display/WTR/JavaScript+Pop+Ups
>
> Jarmo
>
> On Jun 5, 1:05 pm, Babitha wrote:
>
>
>
> > My original code contained an IE.attach to connect to the page where I
> > had the button that was pop opening the javascript dialog.
> > This is what I modified. Not the internal watir code.
>
> > So, in my original code I had to do:
>
> > browser.goto(:url) instead of the IE.attach that I was doing.
>
> > But, I still have this question..is it a known issue?
>
> > On Jun 4, 2:01 pm, Jarmo Pertman wrote:
>
> > > How did you manage to exactly fix it with #goto?
>
> > > Jarmo
>
> > > On Jun 3, 7:32 am, Babitha wrote:
>
> > > > Finally, I found what the issue was.
>
> > > > It is happening because I am using IE.attach to attach to the page
> > > > instead of using browser.Start or browser.goto.
> > > > With browser.goto things started working fine.
>
> > > > Apparently the error message that was logged by the $DEBUG= true
> > > > itself helped me. I saw that internally there is again a call to do an
> > > > IE.attach, and I guessed that may be failing. Please see the relevant
> > > > part of the error message below:
>
> > > > Watir::Button.new(Watir::IE.attach(:hwnd,
> > > > 591236), :unique_number, 4).click!();"
>
> > > > On Jun 2, 1:50 pm, Babitha wrote:
>
> > > > > Trust me. I have done my research. I know there were already many
> > > > > issues reported with element.click_no_wait and most of them are
> > > > > supposed to be fixed. But, I still have this problem with the latest
> > > > > version of watir.
>
> > > > > I am pretty sure with the same version of ruby it worked for me in
> > > > > another system, but as far as I can remember the watir version was an
> > > > > earlier one.
>
> > > > > My current ruby version is 1.86-26 p(111), watir -1.8.1
> > > > > OS: Windows 7, IE 8.
>
> > > > > Here is the problem.
>
> > > > > I have a button on my page, clicking on which it displays a javascript
> > > > > confirmation dialog. I tried it with click() function, and it works
> > > > > fine. But, with click_no_wait() nothing happens, and the control just
> > > > > passes on to the next statement.
> > > > > Below is my code:
>
> > > > > $b = Watir::IE.attach(:url, "myurl")
> > > > > sleep(2)
>
> > > > > btn = $b.button(:id, "btnClear")
> > > > > $DEBUG = true
> > > > > btn.click_no_wait()
> > > > > $DEBUG=false
>
> > > > > My page does not use frames.
>
> > > > > As was suggested in some earlier questions, I put $DEBUG=true and
> > > > > $DEBUG=false statements around the click_no_wait call and below is
> > > > > what I got.
>
> > > > > #no_wait command:
> > > > > Exception `WIN32OLERuntimeError' at c:/ruby/lib/ruby/gems/1.8/gems/
> > > > > watir-1.8.1/lib/watir/element.rb:208 -
> > > > > ruby -e "$:.unshift('c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/
> > > > > watir/win32ole').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > > > > commonwatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > > > > firewatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > > > > watir-1.8.1/lib');require 'c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/
> > > > > lib/watir/core';Watir::Button.new(Watir::IE.attach(:hwnd,
> > > > > 591236), :unique_number, 4).click!();"
> > > > > OLE error code:0 in
> > > > >
> > > > > HRESULT error code:0x80070057
> > > > > The parameter is incorrect.
> > > > > c:/ruby/lib/ruby/gems/1.8/gems/wa
[wtr-general] Re: click_no_wait again
I still don't understand it all exactly. You had a browser object and
ended up on the page where was a button, which created a javascript
dialog upon clicking and then you used #attach for some reason and it
didn't work? #attach should work, i don't see any reasons why it
shouldn't.
But regarding Javascript popups i'd avoid them altogether by
overriding appropriate javascript function at correct place. You can
read more about that from "Simplest way to stop JavaScript Pop Ups
from showing when running your Watir tests" at
http://wiki.openqa.org/display/WTR/JavaScript+Pop+Ups
Jarmo
On Jun 5, 1:05 pm, Babitha wrote:
> My original code contained an IE.attach to connect to the page where I
> had the button that was pop opening the javascript dialog.
> This is what I modified. Not the internal watir code.
>
> So, in my original code I had to do:
>
> browser.goto(:url) instead of the IE.attach that I was doing.
>
> But, I still have this question..is it a known issue?
>
> On Jun 4, 2:01 pm, Jarmo Pertman wrote:
>
>
>
>
>
>
>
> > How did you manage to exactly fix it with #goto?
>
> > Jarmo
>
> > On Jun 3, 7:32 am, Babitha wrote:
>
> > > Finally, I found what the issue was.
>
> > > It is happening because I am using IE.attach to attach to the page
> > > instead of using browser.Start or browser.goto.
> > > With browser.goto things started working fine.
>
> > > Apparently the error message that was logged by the $DEBUG= true
> > > itself helped me. I saw that internally there is again a call to do an
> > > IE.attach, and I guessed that may be failing. Please see the relevant
> > > part of the error message below:
>
> > > Watir::Button.new(Watir::IE.attach(:hwnd,
> > > 591236), :unique_number, 4).click!();"
>
> > > On Jun 2, 1:50 pm, Babitha wrote:
>
> > > > Trust me. I have done my research. I know there were already many
> > > > issues reported with element.click_no_wait and most of them are
> > > > supposed to be fixed. But, I still have this problem with the latest
> > > > version of watir.
>
> > > > I am pretty sure with the same version of ruby it worked for me in
> > > > another system, but as far as I can remember the watir version was an
> > > > earlier one.
>
> > > > My current ruby version is 1.86-26 p(111), watir -1.8.1
> > > > OS: Windows 7, IE 8.
>
> > > > Here is the problem.
>
> > > > I have a button on my page, clicking on which it displays a javascript
> > > > confirmation dialog. I tried it with click() function, and it works
> > > > fine. But, with click_no_wait() nothing happens, and the control just
> > > > passes on to the next statement.
> > > > Below is my code:
>
> > > > $b = Watir::IE.attach(:url, "myurl")
> > > > sleep(2)
>
> > > > btn = $b.button(:id, "btnClear")
> > > > $DEBUG = true
> > > > btn.click_no_wait()
> > > > $DEBUG=false
>
> > > > My page does not use frames.
>
> > > > As was suggested in some earlier questions, I put $DEBUG=true and
> > > > $DEBUG=false statements around the click_no_wait call and below is
> > > > what I got.
>
> > > > #no_wait command:
> > > > Exception `WIN32OLERuntimeError' at c:/ruby/lib/ruby/gems/1.8/gems/
> > > > watir-1.8.1/lib/watir/element.rb:208 -
> > > > ruby -e "$:.unshift('c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/
> > > > watir/win32ole').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > > > commonwatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > > > firewatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > > > watir-1.8.1/lib');require 'c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/
> > > > lib/watir/core';Watir::Button.new(Watir::IE.attach(:hwnd,
> > > > 591236), :unique_number, 4).click!();"
> > > > OLE error code:0 in
> > > >
> > > > HRESULT error code:0x80070057
> > > > The parameter is incorrect.
> > > > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/element.rb:58:in
> > > > `assert_exists': Unable to locate element, using :unique_number, 4
> > > > (Watir::Exception::UnknownObjectException)
> > > > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/
> > > > element.rb:275:in `click!'
> > > > from -e:1
>
> > > > I have gone
> > > > throughhttp://jira.openqa.org/browse/WTR-320andhttp://jira.openqa.org/browse
>
> > > > Can somebody please help me with this?
> > > > Thanks,
> > > > Babitha- Hide quoted text -
>
> > - Show quoted text -
--
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
[wtr-general] Re: click_no_wait again
My original code contained an IE.attach to connect to the page where I
had the button that was pop opening the javascript dialog.
This is what I modified. Not the internal watir code.
So, in my original code I had to do:
browser.goto(:url) instead of the IE.attach that I was doing.
But, I still have this question..is it a known issue?
On Jun 4, 2:01 pm, Jarmo Pertman wrote:
> How did you manage to exactly fix it with #goto?
>
> Jarmo
>
> On Jun 3, 7:32 am, Babitha wrote:
>
>
>
> > Finally, I found what the issue was.
>
> > It is happening because I am using IE.attach to attach to the page
> > instead of using browser.Start or browser.goto.
> > With browser.goto things started working fine.
>
> > Apparently the error message that was logged by the $DEBUG= true
> > itself helped me. I saw that internally there is again a call to do an
> > IE.attach, and I guessed that may be failing. Please see the relevant
> > part of the error message below:
>
> > Watir::Button.new(Watir::IE.attach(:hwnd,
> > 591236), :unique_number, 4).click!();"
>
> > On Jun 2, 1:50 pm, Babitha wrote:
>
> > > Trust me. I have done my research. I know there were already many
> > > issues reported with element.click_no_wait and most of them are
> > > supposed to be fixed. But, I still have this problem with the latest
> > > version of watir.
>
> > > I am pretty sure with the same version of ruby it worked for me in
> > > another system, but as far as I can remember the watir version was an
> > > earlier one.
>
> > > My current ruby version is 1.86-26 p(111), watir -1.8.1
> > > OS: Windows 7, IE 8.
>
> > > Here is the problem.
>
> > > I have a button on my page, clicking on which it displays a javascript
> > > confirmation dialog. I tried it with click() function, and it works
> > > fine. But, with click_no_wait() nothing happens, and the control just
> > > passes on to the next statement.
> > > Below is my code:
>
> > > $b = Watir::IE.attach(:url, "myurl")
> > > sleep(2)
>
> > > btn = $b.button(:id, "btnClear")
> > > $DEBUG = true
> > > btn.click_no_wait()
> > > $DEBUG=false
>
> > > My page does not use frames.
>
> > > As was suggested in some earlier questions, I put $DEBUG=true and
> > > $DEBUG=false statements around the click_no_wait call and below is
> > > what I got.
>
> > > #no_wait command:
> > > Exception `WIN32OLERuntimeError' at c:/ruby/lib/ruby/gems/1.8/gems/
> > > watir-1.8.1/lib/watir/element.rb:208 -
> > > ruby -e "$:.unshift('c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/
> > > watir/win32ole').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > > commonwatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > > firewatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > > watir-1.8.1/lib');require 'c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/
> > > lib/watir/core';Watir::Button.new(Watir::IE.attach(:hwnd,
> > > 591236), :unique_number, 4).click!();"
> > > OLE error code:0 in
> > >
> > > HRESULT error code:0x80070057
> > > The parameter is incorrect.
> > > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/element.rb:58:in
> > > `assert_exists': Unable to locate element, using :unique_number, 4
> > > (Watir::Exception::UnknownObjectException)
> > > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/
> > > element.rb:275:in `click!'
> > > from -e:1
>
> > > I have gone
> > > throughhttp://jira.openqa.org/browse/WTR-320andhttp://jira.openqa.org/browse
>
> > > Can somebody please help me with this?
> > > Thanks,
> > > Babitha- Hide quoted text -
>
> - Show quoted text -
--
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
[wtr-general] Re: click_no_wait again
How did you manage to exactly fix it with #goto?
Jarmo
On Jun 3, 7:32 am, Babitha wrote:
> Finally, I found what the issue was.
>
> It is happening because I am using IE.attach to attach to the page
> instead of using browser.Start or browser.goto.
> With browser.goto things started working fine.
>
> Apparently the error message that was logged by the $DEBUG= true
> itself helped me. I saw that internally there is again a call to do an
> IE.attach, and I guessed that may be failing. Please see the relevant
> part of the error message below:
>
> Watir::Button.new(Watir::IE.attach(:hwnd,
> 591236), :unique_number, 4).click!();"
>
> On Jun 2, 1:50 pm, Babitha wrote:
>
>
>
>
>
>
>
> > Trust me. I have done my research. I know there were already many
> > issues reported with element.click_no_wait and most of them are
> > supposed to be fixed. But, I still have this problem with the latest
> > version of watir.
>
> > I am pretty sure with the same version of ruby it worked for me in
> > another system, but as far as I can remember the watir version was an
> > earlier one.
>
> > My current ruby version is 1.86-26 p(111), watir -1.8.1
> > OS: Windows 7, IE 8.
>
> > Here is the problem.
>
> > I have a button on my page, clicking on which it displays a javascript
> > confirmation dialog. I tried it with click() function, and it works
> > fine. But, with click_no_wait() nothing happens, and the control just
> > passes on to the next statement.
> > Below is my code:
>
> > $b = Watir::IE.attach(:url, "myurl")
> > sleep(2)
>
> > btn = $b.button(:id, "btnClear")
> > $DEBUG = true
> > btn.click_no_wait()
> > $DEBUG=false
>
> > My page does not use frames.
>
> > As was suggested in some earlier questions, I put $DEBUG=true and
> > $DEBUG=false statements around the click_no_wait call and below is
> > what I got.
>
> > #no_wait command:
> > Exception `WIN32OLERuntimeError' at c:/ruby/lib/ruby/gems/1.8/gems/
> > watir-1.8.1/lib/watir/element.rb:208 -
> > ruby -e "$:.unshift('c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/
> > watir/win32ole').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > commonwatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > firewatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> > watir-1.8.1/lib');require 'c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/
> > lib/watir/core';Watir::Button.new(Watir::IE.attach(:hwnd,
> > 591236), :unique_number, 4).click!();"
> > OLE error code:0 in
> >
> > HRESULT error code:0x80070057
> > The parameter is incorrect.
> > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/element.rb:58:in
> > `assert_exists': Unable to locate element, using :unique_number, 4
> > (Watir::Exception::UnknownObjectException)
> > from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/
> > element.rb:275:in `click!'
> > from -e:1
>
> > I have gone
> > throughhttp://jira.openqa.org/browse/WTR-320andhttp://jira.openqa.org/browse
>
> > Can somebody please help me with this?
> > Thanks,
> > Babitha
--
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
[wtr-general] Re: click_no_wait again
Ok I finally found what the issue was. It was due to the IE.attach
that I am using in the code to attach to the page. Once I started
using browser.goto, things started working fine.
Apparently, the error message logged itself helped me identify the
issue. I noticed that internally there is again a call to IE.attach
when click_no_wait is called, and I guessed probably that is the
issue.
Please see the relevant part of the error message below:
Watir::Button.new(Watir::IE.attach(:hwnd,
591236), :unique_number, 4).click!();"
On Jun 2, 1:50 pm, Babitha wrote:
> Trust me. I have done my research. I know there were already many
> issues reported with element.click_no_wait and most of them are
> supposed to be fixed. But, I still have this problem with the latest
> version of watir.
>
> I am pretty sure with the same version of ruby it worked for me in
> another system, but as far as I can remember the watir version was an
> earlier one.
>
> My current ruby version is 1.86-26 p(111), watir -1.8.1
> OS: Windows 7, IE 8.
>
> Here is the problem.
>
> I have a button on my page, clicking on which it displays a javascript
> confirmation dialog. I tried it with click() function, and it works
> fine. But, with click_no_wait() nothing happens, and the control just
> passes on to the next statement.
> Below is my code:
>
> $b = Watir::IE.attach(:url, "myurl")
> sleep(2)
>
> btn = $b.button(:id, "btnClear")
> $DEBUG = true
> btn.click_no_wait()
> $DEBUG=false
>
> My page does not use frames.
>
> As was suggested in some earlier questions, I put $DEBUG=true and
> $DEBUG=false statements around the click_no_wait call and below is
> what I got.
>
> #no_wait command:
> Exception `WIN32OLERuntimeError' at c:/ruby/lib/ruby/gems/1.8/gems/
> watir-1.8.1/lib/watir/element.rb:208 -
> ruby -e "$:.unshift('c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/
> watir/win32ole').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> commonwatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> firewatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> watir-1.8.1/lib');require 'c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/
> lib/watir/core';Watir::Button.new(Watir::IE.attach(:hwnd,
> 591236), :unique_number, 4).click!();"
> OLE error code:0 in
>
> HRESULT error code:0x80070057
> The parameter is incorrect.
> c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/element.rb:58:in
> `assert_exists': Unable to locate element, using :unique_number, 4
> (Watir::Exception::UnknownObjectException)
> from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/
> element.rb:275:in `click!'
> from -e:1
>
> I have gone
> throughhttp://jira.openqa.org/browse/WTR-320andhttp://jira.openqa.org/browse/WTR-459.
>
> Can somebody please help me with this?
> Thanks,
> Babitha
--
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
[wtr-general] Re: click_no_wait again
Finally, I found what the issue was.
It is happening because I am using IE.attach to attach to the page
instead of using browser.Start or browser.goto.
With browser.goto things started working fine.
Apparently the error message that was logged by the $DEBUG= true
itself helped me. I saw that internally there is again a call to do an
IE.attach, and I guessed that may be failing. Please see the relevant
part of the error message below:
Watir::Button.new(Watir::IE.attach(:hwnd,
591236), :unique_number, 4).click!();"
On Jun 2, 1:50 pm, Babitha wrote:
> Trust me. I have done my research. I know there were already many
> issues reported with element.click_no_wait and most of them are
> supposed to be fixed. But, I still have this problem with the latest
> version of watir.
>
> I am pretty sure with the same version of ruby it worked for me in
> another system, but as far as I can remember the watir version was an
> earlier one.
>
> My current ruby version is 1.86-26 p(111), watir -1.8.1
> OS: Windows 7, IE 8.
>
> Here is the problem.
>
> I have a button on my page, clicking on which it displays a javascript
> confirmation dialog. I tried it with click() function, and it works
> fine. But, with click_no_wait() nothing happens, and the control just
> passes on to the next statement.
> Below is my code:
>
> $b = Watir::IE.attach(:url, "myurl")
> sleep(2)
>
> btn = $b.button(:id, "btnClear")
> $DEBUG = true
> btn.click_no_wait()
> $DEBUG=false
>
> My page does not use frames.
>
> As was suggested in some earlier questions, I put $DEBUG=true and
> $DEBUG=false statements around the click_no_wait call and below is
> what I got.
>
> #no_wait command:
> Exception `WIN32OLERuntimeError' at c:/ruby/lib/ruby/gems/1.8/gems/
> watir-1.8.1/lib/watir/element.rb:208 -
> ruby -e "$:.unshift('c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/
> watir/win32ole').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> commonwatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> firewatir-1.8.1/lib').unshift('c:/ruby/lib/ruby/gems/1.8/gems/
> watir-1.8.1/lib');require 'c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/
> lib/watir/core';Watir::Button.new(Watir::IE.attach(:hwnd,
> 591236), :unique_number, 4).click!();"
> OLE error code:0 in
>
> HRESULT error code:0x80070057
> The parameter is incorrect.
> c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/element.rb:58:in
> `assert_exists': Unable to locate element, using :unique_number, 4
> (Watir::Exception::UnknownObjectException)
> from c:/ruby/lib/ruby/gems/1.8/gems/watir-1.8.1/lib/watir/
> element.rb:275:in `click!'
> from -e:1
>
> I have gone
> throughhttp://jira.openqa.org/browse/WTR-320andhttp://jira.openqa.org/browse/WTR-459.
>
> Can somebody please help me with this?
> Thanks,
> Babitha
--
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
