Forum Discussion

Colin_McCrae's avatar
Colin_McCrae
Community Hero
11 years ago

contentDocument.readyState always "complete" in Chrome?

Hi I think this has come up before, but I didn't find any workarounds that I liked the look of? I have a global function I use to wait for pages to load. As you might guess by the thread...
rgratis's avatar
rgratis
Frequent Contributor
11 years ago
Thanks for posting this, Colin.  I've been dealing with browser page load timing issues for months and trying to do things like waiting for page objects, adding delays, etc.  Very time consuming.



It bears mentioning that I really wish TestComplete would build this functionality into the Page.Wait() method.  That method is basically useless in Chrome at the moment.