Extremely strange behavior in Internet Explorer with a large GWT application

I have a loader on my page that gets deleted when I receive a successful response to my RPC. If the RPC call fails, the page is instantly refreshed.

Anytime when I load my page for the first time in IE 7 or 8, it will never load and will never reach the rpc call. Every time I manually update this failed download, it works. I was able to reproduce this about 30 times. This is a problem because the page just sits there with a loader on the screen.

I have no idea what could happen. Try it yourself:

1) Open IE7 or IE8. 2) Go to http://www.foodtrucksmap.com/ 3) The page will be pronounced and will sit there with the loader on the screen forever. 4) Refresh the page and it should work.

I could only come up with one bad solution ... create a timer for 30 seconds, and if the bootloader is still on the screen, refresh the page. I would rather find out what is happening.

UPDATE

As a second workaround, I'm going to add a cookie that expires immediately and reloads if it i.e. first access in a session.

+4
source share
2 answers

I had an unpleasant impression of IE AJAX GET caching, regardless of what we tried.
Where it matters, the best solution we could find was to use POST, which resolved the problem, but is a workaround. Changing the headers to explicitly prohibit caching did not work either.

0
source

Based on what limited information you posted, and what I was able to get from your site, I wonder if you are striking about a request timeout or other server related issue. For example, you downloaded 36 files without javascript compression (35 of which you complete) and all 407 proxy errors.

You should be surprisingly careful with your js file upload order and place script tags. IE is especially sensitive to this.

You have two options:

  • Try adding pending script tags; this should make it load js after loading the content.
  • Since yahoo suggests moving the script tags just above your closing body () tag, then try to find out if that matters. I bet he is waiting for content to be downloaded based on javascript files that haven't finished loading, and all this time is running out.
0
source

All Articles