W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2019

[webrtc-pc] pc.close() should null out currentDirection (#2122)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Thu, 07 Mar 2019 22:58:22 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-418553898-1551999501-sysbot+gh@w3.org>
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc:

== pc.close() should null out currentDirection ==
[stop()](https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-stop) will *"Set transceiver's [[CurrentDirection]] slot to null."*, whereas [close()](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-close) won't. Omission.

Would be great to find a way for *close* to reuse the [stop the transceiver](https://w3c.github.io/webrtc-pc/#dfn-stop-the-rtcrtptransceiver) algorithm *stop* uses here. Unfortunately, they differ on firing the *ended* event.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2122 using your GitHub account
Received on Thursday, 7 March 2019 22:58:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:47 UTC