ESC in Firefox breaks sockjs connection

[majek]

As found out by the Socket.io people:

http://groups.google.com/group/socket_io/browse_thread/thread/a705e4cb532e8808

[majek]

There isn't going to be a fix for that. Users have to cope.

"There isn't going to be a fix for that." Can you elaborate on that?

Currently it completely messes up my UX flow.

[majek]

Sure. This is a well known problem (that's why it's documented). Fixing this is out of the scope for SockJS - that would require messing with user key events, which isn't SockJS responsibility by any means.

I haven't run this in anger, but just catching the esc key in jquery seems to be working fine, please tell me if that works for you:

$('html').keypress(function(e){return e.which !== 0;});

[jwheare]

See also this bugzilla discussion. https://bugzilla.mozilla.org/show_bug.cgi?id=614304

[majek]

@jwheare Great, thanks for the link!

[alp82]

@majek Your workaround causes that F5 is not working anymore in Firefox (tested with FF 11.0 in Ubuntu Linux 64 Bit).

Better use this (taken from the bugzilla link) as a workaround:

window.addEventListener('keydown', function(e) { (e.keyCode == 27 && e.preventDefault()) })

[majek]

@alp82 Brilliant, thanks!

[graue]

Protip for anyone finding this on Google: This is no longer an issue. Mozilla fixed it on the Firefox side.

[Yaffle]

@graue , really?
Did you try while page loading?

[graue]

While the page is still loading, I assume that it will break WebSocket connections :) It'll also break downloading images, CSS and JavaScript. That's what clicking "Stop" or pressing Escape is supposed to do :) But anytime the Stop button is hidden/disabled in Firefox, Escape does nothing at the browser level. So the problem people were talking about in 2011 is gone.