This content has been marked as final. Show 3 replies
From your AIR application, you can only access "exposed properties" in an IFRAME loading content from a different domain.
You expose a property by using the sandbox bridge mechanism: http://livedocs.adobe.com/air/1/devappshtml/help.html?content=security_5.html#1092959
That is, content in the separate domain should have explicitly exposed properties that the parent may access.
But your use case seems genuine though it is very specific. You could submit a feature request for read only access to cross domain content at http://www.adobe.com/go/wish
Thanks for the reply. I don't have any control over the content that is loaded so the ability to expose properties could only happen with content i provide, and given we are talking about any url being referenced then it just isn't possible.
I can guess at what the problem is - it is as if the DOM references are in the context of the loaded page and NOT the environment that encapsulates the html control - okay for web pages but not much use when you are looking to fully inspect the DOM.
I'll submit a feature / bug report.
Thanks for getting back to me
I've never tried dynamically changing the sandboxRoot properties of an iframe, but conceivably you could map a utility html page into the loaded domain. Functions of this utility page could then be used to query the DOM and pass the needed information over the sandbox bridge.