RESOLVED INVALID 32774
Websocket in two tabs stops working when closing the first tab window 
https://bugs.webkit.org/show_bug.cgi?id=32774
Summary Websocket in two tabs stops working when closing the first tab window
Rui Lopes
Reported 2009-12-19 10:35:59 PST
1. Open a page with an websocket that periodically sends data to the browser (eg. it sends the current date 1 time per second). 2. Open the same page in a new tab. 3. Close the first tab (by clicking the tab close button). 4. See that the remaining tab window stops receiving data in the web socket. NB: I can provide a nodejs sample application for this if you want to. NB: This also manifests in chromium, see https://code.google.com/p/chromium/issues/detail?id=30668
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2009-12-20 13:12:39 PST
> NB: I can provide a nodejs sample application for this if you want to. Yes, please do provide a reproducible test case in some form.
Rui Lopes
Comment 2 2009-12-24 05:22:45 PST
These are the steps to get the example working: git clone git://github.com/Guille/node.websocket.js.git cd node.websocket.js node runserver.js --host="" chrome test/test.html And follow the steps I've mentioned on the initial bug report message. BTW, I've tried an equivalent test against a ruby web socket server (http://github.com/igrigorik/em-websocket) and it worked fine. So, maybe there is a problem with the nodejs implementation. I'll check with the author and update this ticket.
Rui Lopes
Comment 3 2009-12-24 10:21:09 PST
This was a problem with node.websocket. Sorry for the noise. FYI, it was reported here: http://github.com/Guille/node.websocket.js/issues/closed#issue/2
Note You need to log in before you can comment on or make changes to this bug.