Hey, During our deployments, we have a small window where both old/new servers could potentially be available. I'm trying to hook into the failure of when a client loads the .nocache.js from one version, but tries to get the permutation from another.
Currently what happens is that the permutation 404s and the GWT app just stops in its tracks, leaving the user with a blank page. I added a onLoadErrorFn, expecting it to be called in this case, but turns out it is not. I put together a patch that changes this: https://gwt-review.googlesource.com/#/c/9510/ It seems fairly straightforward and correctly fires onLoadErrorFn when I purposefully delete a permutation file when running locally to reproduce the behavior. Feel free to either reply with thoughts either here or on the code review. If no one volunteers for the code review, after a few days I'll use git blame to nominate someone. Thanks, Stephen -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/20141005214029.3481030e%40sh9. For more options, visit https://groups.google.com/d/optout.
