Bret, The current method is quite a bit different than the method that I wrote, and I'm not sure it will be as flexible. (For example, you can't attach to a Frame the way you can to an IE or Modal window.) My method is designed to completely re-create the exact method string to get back to the element to be clicked, and is working well for me right now, though there are some inconsistencies with table related elements (which is what got me looking at our current container/collection issue).
I will probably give it another try once trunk settles down a bit and after we get the container/collection settled, but right now I'm getting ready to work on the container/collection issue first. Mark, you may want to look at the modal_dialog branch, which is what I'm using where I work, but right now it's missing a lot of the recent changes to trunk. It's at https://svn.openqa.org/svn/watir/branches/modal_dialog/watir and I'm doing lots of click_no_wait's from within frames. Feel free to contact me if you have questions about the code in that branch as it's pretty much my branch right now and it's probably a dead end until it's decided to port that code to the current trunk. David Bret Pettichord wrote: > This is a "known" problem. (In other words, i knew about it, but it > wasn't well documented.) > > http://jira.openqa.org/browse/WTR-6 > > The fix is for a Watir developer to write attach_command for Frames. > David, this bug is currently assigned to you, but the surrounding code > has changed since you signed up for this. Do you still want to do it? > > BTW, click_no_wait was recently enhanced so that it works in any > context as long as you are not using frames. (If you see otherwise, > please report it). > > Bret _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
