Re: [webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously? (#1883) from Jan-Ivar Bruaroey via GitHub on 2020-03-11 (public-webrtc-logs@w3.org from March 2020)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Mar 2020 15:08:58 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-597689334-1583939337-sysbot+gh@w3.org>

> instead of the dtlsTransport this should also be visible on pc.connectionState (in chrome)

Actually no. The spec says of [`closed`](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnectionstate-closed): _"The RTCPeerConnection object's [[IsClosed]] slot is true."_

...which means it does _not_ detect remote close. Pity. @henbos was this intentional?

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1883#issuecomment-597689334 using your GitHub account

Received on Wednesday, 11 March 2020 15:08:59 UTC