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

Re: Minor: missed one rename of readyState to signalingstatechange

From: Jan-Ivar Bruaroey <jib@mozilla.com>
Date: Thu, 10 Apr 2014 22:00:05 -0400
Message-ID: <53474CA5.6070903@mozilla.com>
To: public-webrtc@w3.org
I have a follow-up request related to something that hasn't been fixed yet:

On 8/5/13 12:44 PM, Jan-Ivar Bruaroey wrote in 
http://lists.w3.org/Archives/Public/public-webrtc/2013Aug/0011.html :
> Just wanted to point out a typo here: 
> http://dev.w3.org/2011/webrtc/editor/webrtc.html#widl-RTCPeerConnection-onsignalingstatechange
>> onsignalingstatechange of type EventHandler,
>>     This event handler, of event handler event type 
>> signalingstatechange, MUST be supported by all objects implementing 
>> the RTCPeerConnection interface. It is called any time the readyState 
>> changes, i.e., from a call to setLocalDescription, a call to 
>> setRemoteDescription, or code. It does not fire for the initial state 
>> change into new.
>
> s/readyState/signalingstate/
>
> readyState was the old name.
>
> Not to be confused with RTCDataChannel.readyState or 
> MediaStreamTrack.readyState (e.g. all other references to readyState 
> in this doc).

The text says: "It does not fire for the initial state change into new." 
- I assume it means "stable".

Here's the request: Please clarify whether it fires for the final state 
change into "closed".

.: Jan-Ivar :.
Received on Friday, 11 April 2014 02:00:33 UTC

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