Some background. There's 20 years of history here. And lots of JIT (Just in Time) learning by doing. That results in a combination of deep understanding and naiveté.
I started going to the sites in raw html and then switched to MSHTML I use any technique that works including looking through temp directories for PDF files and moving the mouse programmatically (yeah, ugly). But about two years ago a security fix broke access to HTTPS sites. I switched to Awesomium and got most things working (and cleaned up a lot) except for some files (at mssb.com banking site) which I haven’t figured out. I tried using the URLs directly and looked for PDF files on disk but to no avail. No surprise that banking sites are challenges.
As to parent/child – my code examples are, of course, limited by the APIs. The new API does look richer – means more learning about using GITHUB beyond NUGET or waiting for the release of 43.
BTW, looking ahead I also need to figure out how to deal with secure iframes.
These issues are why I wrote http://rmf.vc/IEEEAPIFirst but I worry that HTML5 we’re making it increasingly difficult to have a peer relationship. I’m a great fan of HTML5 in general but not at the expense of an API. One of the “features” of HTML5 is to hide relationships to code limiting the utility of the dev tools.