Pages don't refresh until mouse is moved?

[Guest]

Hi

I work in a large corporate using IE6. A lot of us have noticed a strange
intermittent problem over the last couple of months.

We have a large number of web applications (.Net) and are noticing on
various web pages that if we click a link, button or something to cause a
postback, sometimes the IE window doesn't refresh until the mouse is moved.
The window is happy to sit there indefinitely as long as the mouse isn't
moved. As soon as the mouse is moved then the window refreshes to the new
page (or whatever results from the postback).
It has also been noticed after clicking the browser's Back button. Again the
page doesn't redraw until the mouse moves over the client area of the IE
window.

We haven't spotted a pattern to where/when it happens. We mainly use
in-house developed .Net intranet systems, so these are the most commonly
reported problems, however I have also seen it a couple of times on external
sites.

Has anyone else experienced this? I'm assuming from the behaviour that it's
a browser issue and not the sites?

IE details: v6.0.2800.1106CO, SP1; Q867801; Q823353; Q833989; 3283;

Thanks in advance

Andy

 

[Rob ^_^]

Hi Andy,
I am not a big fan of .net form postbacks as I don't think there is a need
to always use this structure for all web forms. There was a previous post
here from Tasmania that experienced the same problem on an onfocus event. I
think this was caused by having two forms on the same page and the solution
was to change one of the forms to a normal post.
I would suggest that you download the Fiddler tool
http://www.fiddlertool.com and check out the chatter of your browsers
requests and responses. My guess is that it is a .net web forms design
issue.
Hope I have been of assistance.
Regards.

 

[Guest]

Thanks a lot. I can't really explain this one away fully, but pointing me in
the direction of Fiddler led me to the problem.

It turns out our site's pages use a javascript which was dynamically adding
a link in the page DOM to a non-existent css file (which was redundant and
therefore not causing any visible issues to visitors). This bad request was
in turn was being redirected to our custom error page which returns a 404. In
Fiddler we could see both the correct page (200) and the error page (404)
coming back to the browser, yet nothing untoward was visible to visitors.

Removing the redundant js code sorted the mouse move issue. Can't really
explain why the 404 would be stopping the new page from rendering in IE until
the mouse was moved, but at least it's fixed.

Andy