That's correct: the click method succeeds where the click_no_wait
method fails.  I'm not entirely sure how to go about checking that, so
can you give me more details? Or, equally, can you provide a button or
a link that you know for sure to be classed as Input rather than with
the <a> tag? Because if you give me an example, I can just write up
some code to check whether the click_no_wait method works for your

On Dec 9, 5:24 pm, Michael Hwee <[EMAIL PROTECTED]> wrote:
> Are you saying when you use 'click', the button was clicked properly?
> The only different between 'click' and 'click_no_wait' is 'wait' statement is 
> removed.
> Can you check to be made sure that is an 'Input', rather than 'a' html tag?
> ----- Original Message ----
> To: Watir General <>
> Sent: Tuesday, December 9, 2008 8:58:46 AM
> Subject: [wtr-general] Re: button.Click_No_Wait only highlights the button, 
> does not click
> Michael - I thought of that already and put in a click_no_wait that
> just selected a link.  Nothing happened, so it wasn't just the popup-
> handling code.  What would a fire_event command look like, exactly?
> Right now, the line that has the problem for me is
> BROWSER.button(:id, "Btndelete").click_no_wait
> Are you saying I should add after that:
> BROWSER.button(:id, "Btndelete").fire_event
> If so, won't that defeat the purpose of having a no_wait command? In
> other words, won't my script then hang instead of executing the popup
> handler?
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To post to this group, send email to
Before posting, please read the following guidelines:
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at

Reply via email to