Webrtc-pc: Processing Remote MediaStreamTracks should pass on receiver when constructing track event

[soareschen]

In the last step of 5.1.1 Processing Remote MediaStreamTracks:

Queue a task to fire an event named track with transceiver, track, and streams at the connection object.

It missed out the receiver attribute in RTCTrackEvent, which we know is simply getting from transceiver.receiver.

[stefhak]

I think this is on purpose, as you say the app can easily get hold of the receiver via the Transceiver.

[jan-ivar]

pc.ontrack = e => e.tranceiver.receiver;

[soareschen]

What I mean is the WebIDL definition for RTCTrackEvent has a receiver field. So that attribute should either be removed or filled with transceiver.receiver, no?

[jan-ivar]

@soareschen Yeah that seems redundant to me. We should remove both the receiver readonly attribute and the corresponding member in RTCTrackEventInit IMHO. Good catch!

[jan-ivar]

Since Firefox already supports e.receiver, we'd continue to for a while for legacy reasons.

[stefhak]

@soareschen got it (https://github.com/w3c/webrtc-pc/issues/1499#issuecomment-319687209). Could you provide a PR?

[jan-ivar]

PR up.

[soareschen]

Thanks @jan-ivar!

@stefhak sorry I am rushing on another project, didn't get the time to work on it.

[jan-ivar]

Doh, I misread @stefhak's message as coming from @soareschen 🙂

[jan-ivar]

I've closed https://github.com/w3c/webrtc-pc/pull/1532.

@soareschen can you add a PR to fill in event.receiver with transceiver.receiver instead?

[stefhak]

Ping @soareschen !