Nope, just the Javascript alert() type. I'm just learning Ruby, so I don't know if it's cool or not, but it sure seemed cleaner than fork'ing.
It is/was on XPSP2 Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Rogers Sent: Wednesday, July 27, 2005 7:14 PM To: [email protected] Subject: RE: [Wtr-general] Pop up handling improvements Ive just seen Scotts post on the 26th and I think I like his solution better. - Scott have you tried all the popup windows - file requester, security etc? What OS did you use? I seem to remember having problems with one type or one os that required a new process rather than a thread. Paul -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Rogers Sent: 27 July 2005 12:31 To: [email protected] Subject: [Wtr-general] Pop up handling improvements The scripts that handle pop ups are in the unit test directory jscriptExtraAlert.rb jscriptExtraConfirmCancel.rb jscriptExtraConfirmOk.rb jscriptPushButton.rb I suggest we move these to a better location - The C:\ruby\lib\ruby\site_ruby\1.8\watir seems like the best place ( or maybe another dir below) We can then maybe add some methods to launch these from watir directly - ie.launch_js_confirm_clicker() Or similar. I think this would be one small step to making these popups easier to deal with. Any suggestions? Paul _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
