I have an asp.net page that is loaded with Farpoint controls and I use Anthem to make callbacks everytime something is changed in any of the cells. So every once and while, I experience an issue where a callback starts up the progress bar. Really, this isn't a problem. The problem is that the progress bar continues to progress slowly, even after the page is complete and ready to use. This gives the users that the page is still doing something and they should wait, a long time, before they start making more edits.
A quick look in google reveiled that the Internet Explorer progress bar was apparently developed by a group of snails, who are not only slow but also of subpar intelligence. At least that's what the community thinks. Google also reveiled this support document. Even Farpoint recognizes this problem and you can read about it here. Here's the gist. When you dynamically insert behaviors in your page, the progress bar gets dazed and confused. If you use the Farpoint spread, you know that this happens a lot. We can set the progress bar back on the right track by writing something to the status bar. I'm guessing that this resets the whole footer in IE.
I am now reseting the status bar on the window.load event and everytime I handle a callback in Anthem. It seems to have corrected my issue.