Have you gone through the settings in IE to make sure it is setup correctly for testing?
See this link
Have you gone through the settings in IE to make sure it is setup correctly for testing?
See this link
Although the problems with IE are solved by this registry hack, it seems a similar problem is also present in Edge.
A redirect seems to destroy the page object, so a function we made to keep checking the page.URL property until it has a certain value fails because after the redirect, the page is gone. This does not happen in IE or Chrome.
I might be able a work around to keep finding all the child pages that are visible while inside the loop, but that seems like a cop out.
WaitPage is not an option btw.
