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

[webrtc-pc] What direction should a stopped transceiver have? #661 (#2479)

From: Armando (armax00) via GitHub <sysbot+gh@w3.org>
Date: Thu, 20 Feb 2020 14:55:13 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-568356436-1582210511-sysbot+gh@w3.org>
armax00 has just created a new issue for https://github.com/w3c/webrtc-pc:

== What direction should a stopped transceiver have? #661 ==
When stop() is executed, or more precisely when the "stop the RTCRtpTransceiver" step[2] is executed, the CurrentDirection slot is updated with a null value. Later, however, is indicated that currentDirection[1] should return "stopped" as a direction if the [[Stopped]] state is true.

This means that while currentDirection is null, the actual value returned would be "stopped".

Shouldn't it make more sense to set the currentDirection state to "stopped" rather then null when RTCRtpTransceiver is executed?

[1] https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-currentdirection
[2] https://w3c.github.io/webrtc-pc/#dfn-stop-the-rtcrtptransceiver

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2479 using your GitHub account
Received on Thursday, 20 February 2020 14:55:14 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:50 UTC