- From: Soares Chen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Jun 2017 08:23:54 +0000
- To: public-webrtc@w3.org
soareschen has just created a new issue for https://github.com/w3c/webrtc-pc: == Public accessor for isClosed == Given that many peer connection methods throw or reject when `[[isClosed]]` is true, it is expected that well designed user applications would want to check the close state as well before calling the methods. Currently there are indirect ways to check the close state of peer connection, by comparing `signalingState`, `iceGatheringState`, etc with the string `"closed"`. But that means there is no one canonical way to check it, and users would have to resort to conventions to check for the closed state. Would it make sense to have a read only attribute `isClosed` on `RTCPeerConnection` to expose the value of `[[isClosed]]`? Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1367 using your GitHub account
Received on Friday, 9 June 2017 08:24:00 UTC