W3C home > Mailing lists > Public > public-webrtc@w3.org > September 2020

[webrtc-pc] Should transceiver.stop() cause transciever.receiver.track.onended to fire? (#2581)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 24 Sep 2020 13:03:35 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-708153215-1600952614-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-pc:

== Should transceiver.stop() cause transciever.receiver.track.onended to fire? ==
When we do pc.close() we explicitly make sure in several places not to fire events. But transceiver.stop() executes "stop sending and receiving", including:

> If disappear is false [which it is], execute the steps for receiver.[[ReceiverTrack]] to be ended. This fires an event.

Was this a mistake or on purpose? I get that it should fire on response to SRD, but transceiver.stop() is a synchronous API.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 September 2020 13:03:37 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 September 2020 13:03:38 UTC