W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2017

[webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Mon, 08 May 2017 23:21:03 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-227202972-1494285662-sysbot+gh@w3.org>
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc:

== End removed tracks remotely again; Make receiver.track nullable instead ==
Instead of https://github.com/w3c/webrtc-pc/issues/1161, let's fire `ended` on remote tracks again like browsers do today, to avoid [breakage](https://github.com/w3c/webrtc-pc/pull/1168#issuecomment-299589165).

Basically, when a `transceiver`'s direction loses the "send" bit as a result of setting a remote description, fire an `ended` event on `transceiver.receiver.track` and set `transceiver.receiver.track` to `null`.

This necessitates making `receiver.track` nullable.

Later, should a transceiver's direction regain its "send" bit as a result of setting a remote description, set `transceiver.receiver.track` to a new track of the same kind, and call [process the remote track](http://w3c.github.io/webrtc-pc/#process-remote-track) (which fires a new `track` event).

This would be backwards compatible.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1181 using your GitHub account
Received on Monday, 8 May 2017 23:21:10 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:50 UTC