Chrome is a bit picky (and rightly so) when it comes to accessing file:/// URIs. You need to deploy to a web server--even if only to serve to localhost.
On Thu, Dec 16, 2010 at 6:21 AM, Pythagoras <[email protected]> wrote: > I executed the Get Started with the GWT SDK. > > Runs fine in Development mode. > > However, when running in production mode, I have 2 problems: > > 1/ Only on Chrome: > The page does not load and I get following error: > Unsafe JavaScript attempt to access frame with URL > file:///C:/Program%20Files/Google/gwt-2.1.0/StigTable/war/StigTable.html > from frame with URL > > file:///C:/Program%20Files/Google/gwt-2.1.0/StigTable/war/stigtable/028100D2D82D5408B73F9CBFD379177D.cache.html. > Domains, protocols and ports must match. > > > 1/ On other browsers, the page loads, but after pushing the button, I > get following error: > Server replies: > An error occurred while attempting to contact the server. Please check > your network connection and try again. > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
