Forum Discussion
Colin_McCrae
11 years agoCommunity Hero
I believe I have a solution.
The "reload" button in the Chrome toolbar can be used.
While the page is busy, it changes the description text on the button to "Stop loading this page". Once complete, this changes to "Reload this page". Net effect is the same as checking the readyState in IE.
The project is already cross browser so has the browser in use stored in a global variable. So the wait for page load routine will use this to determine whether to use readyState (IE) or the reload button (Chrome).
Main thing to be careful of is if you are using multiple browser during the test as you need the BrowserWindow(<num>) object to get to the reload button. But you can either track this yourself or backtrace it using the content of the Address/Search bar to find the parent BrowserWindow you want.
Either way, it works and I can use it throughout the test(s).
Happy days. :)
The "reload" button in the Chrome toolbar can be used.
While the page is busy, it changes the description text on the button to "Stop loading this page". Once complete, this changes to "Reload this page". Net effect is the same as checking the readyState in IE.
The project is already cross browser so has the browser in use stored in a global variable. So the wait for page load routine will use this to determine whether to use readyState (IE) or the reload button (Chrome).
Main thing to be careful of is if you are using multiple browser during the test as you need the BrowserWindow(<num>) object to get to the reload button. But you can either track this yourself or backtrace it using the content of the Address/Search bar to find the parent BrowserWindow you want.
Either way, it works and I can use it throughout the test(s).
Happy days. :)
Related Content
- 6 years ago
Recent Discussions
- 7 hours ago