W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2014

[Bug 25892] New: SignalingStateChange event should be fired only if there is a change in signaling state.

From: <bugzilla@jessica.w3.org>
Date: Tue, 27 May 2014 10:11:46 +0000
To: public-webrtc@w3.org
Message-ID: <bug-25892-4991@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25892

            Bug ID: 25892
           Summary: SignalingStateChange event should be fired only if
                    there is a change in signaling state.
           Product: WebRTC Working Group
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebRTC API
          Assignee: public-webrtc@w3.org
          Reporter: kiran.guduru@samsung.com
                CC: public-webrtc@w3.org

SignalingStateChange event is being fired as a result of setLocalDescription /
setRemoteDescription.
But there are cases where signaling state will not be changed as a result of
setLocalDescription / setRemoteDescription, for example.

pc.createOffer()
pc.setLocalDescription()
onSignalingStateChange() -- Event fired as a result of signaling state change
// Again if createOffer is called for second time.
pc.createOffer()
pc.setLocalDescription()
// There is no change in the signaling state but still onSignalingStateChange()
event is firing.

Spec should modify text in setLocalDescription step 7 from


Fire a simple event named signalingstatechange at connection.

to 

Fire a simple event named signalingstatechange at connection, if signaling
state is changed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Tuesday, 27 May 2014 10:11:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:40 UTC