[webrtc-pc] pc.close() almost stops transceivers fully.

• From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
• Date: Fri, 15 Jun 2018 06:23:11 +0000
• To: public-webrtc-logs@w3.org
• Message-ID: <issues.opened-332658960-1529043790-sysbot+gh@w3.org>

jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc:

== pc.close() almost stops transceivers fully. ==
pc.[close()](http://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-close) rolls its own version of **stop transceiver** that is almost—but not quite—identical to tc.[stop()](http://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-stop).

The difference looks accidental: It forgets to set [[Receptive]]=false and [[CurrentDirection]]=null.

These somewhat recent additions look like they got out of sync.

We probably want to rewrite this to reference a common algorithm.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1894 using your GitHub account

Received on Friday, 15 June 2018 06:23:15 UTC