all of those are methods ( or properties of IE )

http://msdn2.microsoft.com/en-us/library/aa752043.aspx
and
http://msdn2.microsoft.com/en-us/library/ms534359.aspx
  ----- Original Message ----- 
  From: Jeff Fry 
  To: [email protected] 
  Sent: Tuesday, June 19, 2007 7:38 PM
  Subject: [Wtr-general] Understanding IE's wait method


  Hey gang,

  I am reading through IE's wait method, and (A) very impressed by all we are 
tracking, and (B) confused by a few bits.

  I've been searching for but am unable to find the definition of the .busy and 
.readyState methods IE is calling. Can you let me know where they are declared 
(and ideally, how I might discover where they're declared). I assume they are 
included from something else, but I couldn't figure out where. 

  On a high level, my understanding of wait is that it waits for ie.busy to be 
false, then for ie.readyState to equal READYSTATE_COMPLETE...which seems to == 
4. I'd love to know what's meaningful about 4 here (say, as opposed to 42). 
Then it waits for the main document to exist (to be true). 

  At this point it creates the documents_to_wait_for array, and initializes it 
with the main document for the page.

  Next I see we wait until doc.readyState == "complete". Again, here I'm 
stumped as to what .readyState is doing. After compiling the list of urls for 
the page, we go through each frame and wait for the document for each frame to 
load. When that is done, we record @down_load_time.

  Thanks!
  Jeff

  -- 
  http://testingjeff.wordpress.com 


------------------------------------------------------------------------------


  _______________________________________________
  Wtr-general mailing list
  [email protected]
  http://rubyforge.org/mailman/listinfo/wtr-general
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general

Reply via email to