Closed Bug 1141726 Opened 11 years ago Closed 11 years ago

signalingstatechange is fired after success callbacks for SetLocal/SetRemote

Categories

(Core :: WebRTC: Signaling, defect)

Product:
Core
Component:
WebRTC: Signaling
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: bwc, Assigned: bwc)

Details

The spec says we should handle the signaling state change before firing the success callback.
Assignee: nobody → docfaraday
Looks like some queuing in PeerConnection.js makes this work.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.