iframes are quite difficult to manage. Policies about parent page-iframe son communications are quite strict. In fact you can access to the iframe's context(window's properties and document) only when main page and iframe shares the same domain. In case domains differ , inspecting the frame is impossible and the iframe cannot access to the parent's context document.
There is only one cache, the ONLY provided information is the first iframe's URL. The iframe is a sandbox which should protect cookies and other information from being predated, an evil site could youse sniffing URL changes in order to track user's navigation. Let's think about sites which uses generated URL in order to provide dynamic pages. I think you get the reason about hiding the URL's changes. The are 2 main situation: 1)The iframe and page share the same domain (e.g: www.site.com) --> you have fully access to all the document's stuff. 2)The iframe and page don't share the same domain --> nothing to do, only the initial URL could be retrieved, accessing to other objects or properties should rise an exception. Regards -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
