26620 2014-08-20 21:37:05 +0000 getStats should be allowed on a closed PeerConnection. 2014-10-31 18:30:42 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified PC Linux RESOLVED MOVED P2 normal --- 1 harald vsingh.ietf dom public-webrtc oldest_to_newest 110372 0 harald 2014-08-20 21:37:05 +0000 From Jan-Ivar Bruarøy: I'd like to propose a change to getStats so that calling it on a closed PeerConnection does not throw, but instead gives you the stats at the time the PeerConnection closed. Use-case: A webpage wants stats about the call that just terminated from the other side - e.g. how many frames dropped? In [1] remove step 1: > 1. If the RTCPeerConnection object's RTCPeerConnection signalingState is closed, throw an InvalidStateError exception. And edit step 5 (which would now be 4): > 4. Start gathering the stats indicated by selectorArg. In case selectorArg is null, stats MUST be gathered for the whole RTCPeerConnection object. If the RTCPeerConnection object's RTCPeerConnection signalingState is closed, stats should reflect the state at or near the time that signalingState transitioned to closed. Implementations would basically cache a final call to getStats internally as part of transitioning to closed. .: Jan-Ivar :. [1] http://dev.w3.org/2011/webrtc/editor/webrtc.html#methods-5 114393 1 harald 2014-10-31 18:27:31 +0000 Since we're moving the stats API to the stats document, this can be done there. This issue should be moved to Github. Dom will. 114394 2 dom 2014-10-31 18:30:42 +0000 Filed at https://github.com/w3c/webrtc-stats/issues/3 ; closing for WebRTC