Did some more digging and noticed that the document's readystate is still set to interactive even though there isn't anything still waiting to be loaded.
On Jan 29, 10:30 am, Paul Rogers <[email protected]> wrote: > watir will wait until the browser reports that it has finished, so if > its still rendering, or waiting on content from code written by the > javascript, it will still wait. Other things like, iframes and ajax > may also affect this. > > It may appear to us that the page has finished, but the browser is > still doing stuff. > > Several times there has been talk of adding a timeout on the wait > code, but I dont know if anything has ever been done with it > > Paul > > On Thu, Jan 29, 2009 at 11:08 AM, Bach Le <[email protected]> wrote: > > > Note that the same thing happens when navigating towww.microsoft.com. > > Using fiddler, I'm able to determine that my sample fully loads the > > webpage in about 15 seconds. Meaning every time in the page has fully > > loaded including ones loaded via external javascript. > > > However Watir doesn't return until about the 40 sec mark which means > > it's waiting around for an additional 25 seconds. Something seems > > wrong here. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Watir General" group. To post to this group, send email to [email protected] Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/watir-general -~----------~----~----~----~------~----~------~--~---
