I asked our developers about this and it turns out that with Dot-Net, IE sometimes reports that it is done before it is finished drawing all the frames. (I had even reported some bugs in our app about this a while ago - the delay can be up to several, noticeable seconds sometimes.)
So on some pages, it makes sense that I have to insert a sleep/wait command of some sort. I'll finish the script and then think about refactoring it to include checks like the one above to make it smarter about waiting for certain pages to appear before proceeding.
By design, Watir should dependably wait for frames to load even when IE incorrectly reports that it is done. Clearly that isn't working correctly for your application.
If you can give more specific information about your app and how you're able to workaround the issue, that would be helpful.
Bret
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
