I am familiar with attempting to wait for certain objects to become available, but this approach would require me to write separate code to verify every page transfer because the unique objects available would differ based on the page. Searching for common application page objects has the same problem as Page.Wait; WaitChild/FindChild sometimes return the object from the old page, before the new content has loaded.
I was really looking for a global function that would wait for a page load. The code I came up with is a bit of a hack, but it fixes the issues with Chrome 30+ and the Page.Wait function.
Another approach could be to get a reference to any top-level panel object on the original page, then wait for it to not exist (meaning the page load has occurred). I might explore this today if I have some spare time, as it would be preferable to messing around with Chrome's contentDocument and not require separate handling based upon browser.