IE7/IE8 Loading Bar #491

wilkinsonj opened this Issue Jun 28, 2012 · 9 comments


None yet

5 participants


IE7 and IE8 both show a continuous loading bar after connecting.

There must be a way around this because the same does not happen on


You might want to take a look at #215, redsquare posted a code snippet there that should fix the problem. As David was not able to repro the issue, please try it and see if it works for you and report back.


I have tried the code posted.

It partially solves the problem, but not completely.

The loading symbol is gone from the tab, but the status bar still reads 'waiting for ...'


FYI - the way Socket.IO gets around this issue is as follows:

The HTMLFile transport creates a forever iframe based transport for Internet Explorer. Regular forever iframe implementations will continuously trigger the browsers buzy indicators. If the forever iframe is created inside a htmlfile these indicators will not be trigged.

SignalR member

Send a pull request.


Some background info on ForeverFrame using htmlfile in IE:

The downside is that this "solution" only works in IE...

SignalR member

That's fine. IE is the only browser that uses forever frame anyways.

@NTaylorMullen NTaylorMullen was assigned Aug 3, 2012
@NTaylorMullen NTaylorMullen added a commit that referenced this issue Aug 4, 2012
@NTaylorMullen NTaylorMullen Fixed #215, #383 and #491
All the bugs fixed in this commit are duplicates.

Executing Javascript once the DOM yielded constant loading in some
browsers where they viewed the page as continuously loading since the
entire page had not been loaded, even though the DOM had.  Fixed this
issue by re-routing the connection.start call to the window.load event
by default but also allowing the user to overwrite the default via the
startAfterPageLoad flag.

Duplicate of #215


@davidfowl The loading symbol is gone from the tab, but the status bar still reads 'waiting for ...' you know if there is any work around to remove this status bar.
you mentioned 'Send a pull request.' how to do that?

SignalR member

@ramaila I have no idea what the workaround is.

Information on pull requests:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment