Closed
Bug 878562
Opened 12 years ago
Closed 11 years ago
not event "closed" of RTCIceConnectionState if a remote user is disconnected (quit browser, refresh by F5, ...)
Categories
(Core :: WebRTC: Networking, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 852665
People
(Reporter: synpp, Unassigned)
Details
(Whiteboard: [WebRTC][blocking-webrtc-])
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.20 Safari/537.36
Steps to reproduce:
not event "closed" of RTCIceConnectionState if a remote user is disconnected (quit browser, refresh by F5, ...)
Actual results:
not event "closed" of RTCIceConnectionState if a remote user is disconnected (quit browser, refresh by F5, ...)
Expected results:
not event "closed" of RTCIceConnectionState if a remote user is disconnected (quit browser, refresh by F5, ...)
Updated•11 years ago
|
Component: Networking → WebRTC: Networking
QA Contact: jsmith
Comment 1•11 years ago
|
||
I'm confused by this bug.
Are you saying that no event is firing when the remote user has closed their connection and the ice connection state has gone to closed?
I'm guessing the event you are referring to here is probably oniceconnectionstatechange, correct?
Flags: needinfo?(synpp)
Updated•11 years ago
|
Whiteboard: [WebRTC][blocking-webrtc-]
Updated•11 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•