Hi all,
I figured out the issue. The popup which had the button for opening
the modal dialog had a drop down list and the button which opened the
modal dialog. When a value is selected from the drop down list, the
pop up reloads. So, I had to attach the popup again, before I used
click_no_wait and
Hi,
I had a similiar problem that began when I started using IE8. I found
(and could be wrong) that WinClicker didn't seem to handle the popup,
so, I am now using the method clickprompt which I borrowed from
http://wiki.openqa.org/display/WTR/JavaScript+Pop+Ups
It works for IE8 and IE7.
--
Befo
Hi all,
Thanks for all the posts. I am not really trying to access the button
by using unique_number. The click_no_wait function in element class
passes the command to spawned_click_no_wait_command which refers to
the element using unique_number.
I have seen the example on the page:
http://wiki.
You're right, I don't really need to do that. Thanks for helping out!
--A. Vuori
On 1 joulu, 10:38, Jarmo Pertman wrote:
> Why are you running your tests in $DEBUG mode anyway? There should be
> a lot of information in your console if $DEBUG is enabled all the
> time. Do you really need it? It
Why are you running your tests in $DEBUG mode anyway? There should be
a lot of information in your console if $DEBUG is enabled all the
time. Do you really need it? It seems to me that you're just doing it
wrong if it's enabled for your whole testsuite...
You can monkey-patch that if it's really n
Ah, there seems to be a design decision between debugging
click_no_wait output and breaking the method in debug mode. The latter
was confusing, the former was on the other hand very helpful
initially. Could there be another way of debugging the output of
click_no_wait, as now it is not possible to
Arto Vuori:
#click_no_wait is only blocking intentionally when $DEBUG is true. As
soon as you use it normally (e.g. $DEBUG being false) then "start
rubyw" is used to perform the click itself thus the change made by you
should not be needed and it should work without that either. Just make
sure that
I'd suggest looking at some of the other solutions listed here:
http://wiki.openqa.org/display/WTR/JavaScript+Pop+Ups perhaps one of
them will work better.
Otherwise specific answers to each step of the IRB process that Jarmo
suggests, (are you getting the right hwnd, etc) might help to figure
ou
Hi,
thanks for helping us out, Jarmo!
I learned that if I attach to an IE process that is not opened by
Watir::Browser.New, watir is able to locate the Window by its hwnd and
attach to it.
After this the problem was that the newly created ruby process itself
blocked blocking the main process wel
Hi Jarmo,
Thanks for your post.
But, I still get the same error i.e.
"Watir::Exception::UnknownObjectException: Unable to locate element,
using :unique_number, 1" when I use:
require "watir"
b = Watir::Browser.attach :title, /title/
b.button(:unique_number, 1).click
Thanks.
Kushal
On Nov 25,
#click_no_wait returning nil is a correct behavior. Open up the page
in your browser where that button is and then open up an irb session
and try this:
require "watir"
b = Watir::Browser.attach :title, /title/
b.button(:unique_number, 1).click
Does that do anything or does it throw the same error
Hi Kushal,
I'm having exactly the same problem and I have not found a working
solution.
I have a need to open and interact with a modal dialog. However,
click_no_wait simply returns nil.
-- A. Vuori
On 21 marras, 20:29, Kushal wrote:
> Hi all,
>
> I am stuck in this problem for three days now.
Anyone? And I forgot to mention that I am using IE7.
Thanks.
Kushal
On Nov 21, 12:29 pm, Kushal wrote:
> Hi all,
>
> I am stuck in this problem for three days now. I need to open a modal
> dialog from a button on a webpage. When I use click or
> fire_event("onclick"), execution just hangs. This
13 matches
Mail list logo
