Gems prior to 1.5.1.1166 would either give me the access denied errors as it tried to wait for the inner frames to load - or if those were suppressed, I had to put in a manual wait whenever I navigated to a new page: "sleep 0.1 until some_element_on_inner_frame.exists?". After installing 1166 all of these delay problems were fixed... Until now.
Now that this issue has surfaced I'm forced to put the manual delays in again. It is not a big deal to do this, but, it's always cleaner if watir handles the delays properly. -David ---------------- From: Bret Pettichord <[EMAIL PROTECTED]> Brown, David wrote: > I've been using the development gem 1.5.1.1166 which includes the > re-written wait logic to test a complex SAP web application. The main > content that I am automating is nested 4 frames deep. Up until this > past Friday this version of watir seemed to handle waiting for all of > the inner frames to load properly. Now however this wait logic isn't > always waiting until the pages load completely which causes my scripts > to fail. I don't think there have been any changes in the web app I'm > testing which would cause this. I did happen to install the > important/critical Microsoft security patches for June which could > have effected watir? > http://www.microsoft.com/technet/security/bulletin/ms07-jun.mspx > > Has any one else experienced this problem with the new wait logic not > waiting quite long enough when there are many nested frames? > What happens if you use an earlier Watir gem, before we rewrote the frame wait logic? Bret _______________________________________________ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
