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 ---- From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> To: Watir General <watir-general@googlegroups.com> 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 watir-general@googlegroups.com Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/watir-general -~----------~----~----~----~------~----~------~--~---
