> The reason for my concern is that this error is in
> check_for_http_error. This method isn't called until after all the
> wait checks are complete and Watir thinks that the page is already
> fully loaded. So that means that there is a bug in the core wait code.
Not necessarily. I have pages in my web scraper that load and then
immediately run code to load a *different* page, just like a redirect.
Yes, this is ugly and not great web design, but it is being done. If
Watir is still checking return codes on the first page while IE starts
the process to load the NEXT page then the COM document method may not
be valid when we're still trying to check the results of the first page
load.
My understanding is that Watir will wait in this situation. It is designed to do this. Are you saying it doesn't? Can you give us an example?
I suspect that this isn't a common occurrence, which is why it hasn't
shown up frequently in the past.
Without actually knowing details from the OP, how can you make this assumption? What questions would you need to ask in order to confirm this suspicion?
In addition, wasn't the code to check
the status of loaded frames added only recently?
Not at all. It's been in there a long time. It is in 1.4.1. Please take a look at the history of the code (which is all in SVN) instead of making assumptions about it.
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
