The case I have encountered for using click!, is when 'click' doesn't
return for a long time (or sometimes never depending on how buggy a
web page or ad-servers are), and a 'click!' followed by a 'wait_until'
to check the event success/fail is sufficient.
--Shane.
On Oct 13, 12:44 pm, Bret
Shane wrote:
The case I have encountered for using click!, is when 'click' doesn't
return for a long time (or sometimes never depending on how buggy a
web page or ad-servers are), and a 'click!' followed by a 'wait_until'
to check the event success/fail is sufficient.
That makes sense to
For Watir, the difference is that while click! does it's execution in
the same ruby process, click_no_wait actually creates a new ruby
script to attach to the current IE window and click on the specified
control, and executes that in a completely new process using
rubyw.exe.
The problem this
Shane wrote:
So if no IE modal dialogs pop up, I would recommend you use click!,
because you don't have the overhead of starting up a new ruby process
each time.
And that has worked for me so far.
In this case, i would recommend using plain old click. I have not seen
a use case for
Hi
We have installed ruby 1.86-26 only, but whats exactly difference between
these two methods?
Please let me know.
On Fri, Oct 9, 2009 at 8:56 PM, Charley Baker charley.ba...@gmail.comwrote:
The one major reason that click! would work and not click_no_wait is if
you've installed from the
The one major reason that click! would work and not click_no_wait is if
you've installed from the ruby one click installer 1.8.6.27 rc2. Try the
previous version 1.8.6.26.
-c
On Thu, Oct 8, 2009 at 11:06 PM, Pallavi Sharma write2pall...@gmail.comwrote:
Hi
Can anyone here tell me what are the
