I have been able to simulate the problem by causing a 404 when the
*.cache.html is requested.
Stepping through firebug, this is the relevant code in
the .nocache.js:
22 function maybeStartModule(){
23 if (scriptsDone && loadDone) {
scriptsDone is never true because the script is no longer available,
which is happening when the cache.html gets blocked by a firewall.
Therefore our application stays in a perpetual "loading application"
page which isn't a good look.
Is there a way to test whether the cache.html file has the correct
content, assuming there is a way to wait for it to load completely?
Joe
On Aug 5, 1:33 am, Joe Cole <profilercorporat...@gmail.com> wrote:
> When debugging a customer who couldn't load our site with an http
> connection (worked fine on ssl as it bypassed the firewall) we came
> across an issue where if we tried to load the *.cache.html file gwt
> was trying to load manually the companies firewall had displayed an
> error message. There was no error on the gwt side, so we were unable
> to provide feedback to the user.
>
> Is it possible to write something in the nocache.js that checks that
> the *.cache.html that is loaded is actually what we expect, and if
> not, we can get an error message back to the user in some way?
>
> Currently we use the following method for detecting load errors, but
> they aren't being called. Could it be tied into this in some way?
>
> <meta name="gwt:onLoadErrorFn" content="loaderror"></meta>
> <meta name="gwt:onPropertyErrorFn" content="unsupported"></meta>
>
> <script type="text/javascript">
> <!--
> // Called when GWT is not supported
> function unsupported() {
> document.getElementById('loading').className
> = "loadError
> message-center-screen";
>
> document.getElementById('loading-content').innerHTML = "Your
> browser is not supported. Please reload with a modern browser such as
> <a href=\"http://www.getfirefox.com\";>Firefox</a> or Internet Explorer
> Version 6 or Above.";
> }
> function loaderror(){
> document.getElementById('loading').className
> = "loadError message-
> center-screen";
>
> document.getElementById('loading-content').innerHTML = "Error:
> There was a problem loading the application.";
> }
> -->
> </script>
>
> E.g. a new meta property could be added that tells us the cache file
> is not able to be loaded, with the name of the cache file so we can
> show them the error by opening it in a new window so they can see the
> error message.
>
> Joe
--~--~---------~--~----~------------~-------~--~----~
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-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
-~----------~----~----~----~------~----~------~--~---
