Yeah, I just wasn't thinking in that direction - at all. When two browsers have no difficulty loading my local files and then Chrome shows some stuff but not the widgets, then I suspected a bug in the latest GWT or browser version maybe. Now that I know, I'll just upload to the server, no biggie.
>On Oct 3, 4:45 pm, Thomas Broyer <[email protected]> wrote: > 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
