25892 2014-05-27 10:11:46 +0000 SignalingStateChange event should be fired only if there is a change in signaling state. 2014-06-09 08:47:07 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified All All RESOLVED FIXED P2 normal --- 1 kiran.guduru public-webrtc adam.bergkvist public-webrtc oldest_to_newest 106830 0 kiran.guduru 2014-05-27 10:11:46 +0000 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. 107241 1 adam.bergkvist 2014-06-04 08:32:10 +0000 I believe you are right. Proposed fix: https://github.com/fluffy/webrtc-w3c/commit/406f1aa7248583e8823d3560e61c3060f75a8e69