Please clarify whether onsignalingstatechange fires for the final state change into "closed"

Sorry, I buried my lead:

Please clarify whether onsignalingstatechange fires for the final state 
change into "closed".

.: Jan-Ivar :.

On 4/10/14 10:00 PM, Jan-Ivar Bruaroey wrote:
> 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 :.
>