Also, page.RefreshMappingInfo() might help...
Also, page.RefreshMappingInfo() might help...
It's also possible that subsequent pages are not actually pages, rather they may be frames or sub-elements of a single page. Hard to say without seeing it.
But you can detect that as well. You can use the "ready state" of the page. This will/should only go to complete once EVERYTHING on the page has completed loading. Including sub-page-level events. On IE, this works fine. On Chrome, there is a bug in that it always shows "Ready" even if the page is still loading. It's a known bug in Chrome and has been there a LONG time. (it may have been fixed now, been a while since I looked) As a workaround, you can watch the page loading spinner on Chrome instead and wait for that to change. I've used this method in the past for pages with AJAX events on them and it works great.
I'll have to try the refresh mapping to see if that works.
Each page is mapped with the object type of Page and a dynamic URL.
andrewa wrote:
I'll have to try the refresh mapping to see if that works.
Each page is mapped with the object type of Page and a dynamic URL.
Yeah, that mapping SHOULD work to uniquely identify all the pages... but a refresh mapping info will certainly make sure that the cached mapping information is cleared. If that doesn't work, let us know and we'll figure something out. :)
