If you're opening the file off the filesystem (rather than served by an HTTP server)n then that's the expected behavior (and expect other browsers to follow Chrome in the future). This is because each file:// URL should have its own origin; loading a *.cache.html in an iframe and trying to make it access its parent (as GWT does by default) thus violates the Same-Origin Policy.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/kbgNgFeL4asJ. To post to this group, send email to google-web-toolkit@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.
