Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

0.5.1 ForeverFrame reconnect error: null frame reference #447

Closed
jfollas opened this Issue Jun 13, 2012 · 4 comments

Comments

Projects
None yet
3 participants

jfollas commented Jun 13, 2012

Upgraded to 0.5.1 from 0.5rc, and I'm debugging on localhost (using VS2010 to debug IE9 client-side code).

If I navigate off of a page that is connected to a hub, then VS2010 trips into the debugger within the following ForeverFrame reconnect code block because connection.frame is null (so trying to set frame.src fails).

reconnect: function (connection) {
    var that = this;
    window.setTimeout(function () {
        var frame = connection.frame,
            src = transportLogic.getUrl(connection, that.name, true) + "&frameId=" + connection.frameId;
        connection.log("Upating iframe src to '" + src + "'.");
        frame.src = src;
    }, connection.reconnectDelay);
},
Owner

davidfowl commented Jun 13, 2012

Does it happen when you're not debugging? Are all the scripts properly updated? Is this using IE10?

jfollas commented Jun 13, 2012

IE 9 (on Win7)

No errors when I access the site using IE9 once deployed to a webserver, so the error is only while debugging from localhost (ASP.NET 4.0/IIS Express)

Used NuGet to update SignalR, double-checked script references to ensure pointing at 0.5.1 (they are).

Exact error message (due to the null frame reference):

"Microsoft JScript runtime error: Unable to set value of the property 'src': object is null or undefined"

I too get the same error while debugging - same machine setup as well.

Owner

davidfowl commented Jun 16, 2012

This is a duplicate of #446

@davidfowl davidfowl was assigned Jun 16, 2012

@davidfowl davidfowl closed this Jun 16, 2012

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