Sorry, you are right, I did get the links wrong. The first link should have been http://msdn.microsoft.com/en-us/library/ms534360%28VS.85%29.aspx which applies to "OBJECT" types, whatever that means (but does include Watir's @ie object). My actual first link is to XMLHttpRequest documentation, which is not at all relevant to this discussion.
The second link, for document and frame objects, was correct. -Ethan On Tue, Feb 16, 2010 at 17:09, Bret Pettichord <[email protected]> wrote: > I am confused. Is it possible that you mixed up the two links to the > Microsoft docs? The first says a readystate of 3 means the object is not > available, whereas the second says that 3 means it is. > > Bret > > On Tue, Feb 16, 2010 at 3:13 PM, Ethan <[email protected]> wrote: > >> Watir::IE#wait checks that @ie.readyState == READYSTATE_COMPLETE, where >> READYSTATE_COMPLETE is 4. >> >> I'm running into issues where, after completing a file download, >> @ie.readyState is 3. >> >> The relevant documentation for this property seems to be at >> http://msdn.microsoft.com/en-us/library/ms534361%28VS.85%29.aspx(although I >> do not known precisely whan an "OBJECT" is in this context, it >> seems to apply to the @ie object). >> >> aside: that is not to be confused with the readyState property of a >> document, which is slightly different and is documented here: >> http://msdn.microsoft.com/en-us/library/ms534359%28VS.85%29.aspx >> the readyState of the document is "complete" in this case, despite the >> readyState of the browser being 3 which corresponds to "interactive". >> >> Since a readyState of 3 means "User can interact with the object even >> though it is not fully loaded.", should that not be a valid state for Watir >> to consider the browser to be ready? >> >> I'm not sure why that description applies to the browser after a file >> download completes - maybe it shouldn't? maybe it's an IE bug? >> But, it does seem to me that that description describes a state where it >> should be ready for Watir to interact with it, so perhaps that check should >> be changed to @ie.readyState >= 3. >> Likewise, maybe the checks for the document's readyState (and that of all >> its frames) should be changed to check if it is either "complete" or >> "interactive"? Although I have not seen the 'interactive' state come up in >> my own experience. >> >> -Ethan >> >> >> _______________________________________________ >> Wtr-development mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/wtr-development >> > > > > -- > Bret Pettichord > Lead Developer, Watir, www.watir.com > > Blog, www.io.com/~wazmo/blog <http://www.io.com/%7Ewazmo/blog> > Twitter, www.twitter.com/bpettichord > > > _______________________________________________ > Wtr-development mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-development >
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
