There are several different approaches to this - I'd start with the examples on the pop-up FAQ pages, hopefully one of them will work for you:
http://wiki.openqa.org/display/WTR/JavaScript+Pop+Ups http://wiki.openqa.org/display/WTR/Pop+Ups http://wiki.openqa.org/display/WTR/Security+Alerts When dealing with dialogs that block the browser window, the common thread (no pun intended, I swear!) in each approach is to start a separate process to send input to the dialog _before_ sending the click (or other input) that will cause the dialog to appear. This is where things get confusing, since there are several different ways to launch a detached, separate process, and many, many different ways to implement a separate "popup killer" program. But it can be made to work. :) Thanks Bill On Mon, Apr 12, 2010 at 6:07 PM, Rats <[email protected]> wrote: > Given I simply cannot get click_no_wait working with my current > configuration are there any other ways of handling js popups? > > Currently I'm using: > > Win7 > IE8 > Watir 1.6.5 > Ruby 1.8.6 (1 click installer version) > > -- > Before posting, please read http://watir.com/support. In short: search > before you ask, be nice. > > You received this message because you are subscribed to > http://groups.google.com/group/watir-general > To post: [email protected] > > To unsubscribe, reply using "remove me" as the subject. > -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. You received this message because you are subscribed to http://groups.google.com/group/watir-general To post: [email protected]
