Closed Bug 743623 Opened 12 years ago Closed 12 years ago

websocket tab disconnect

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
11 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: torleifw, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.151 Safari/535.19

Steps to reproduce:

Create multiple instances (tabs) of the same websocket. Disconnecting or closing one tab will close all other connections. 


Actual results:

All pages & sockets called the socket.onclose() function, closing all connections on all tabs.


Expected results:

Only the disconnected or closed tab should call the onclose function. Google Chrome handles this event properly.
Update: The closed sockets was caused by a server returning invalid frames. While this means there may be a bug that could close all open sockets on firefox at one time, it's probably not big a deal.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.