Feature: Support RTCTrackEvent

[ChaitanyaPTank]

Currently RTCTrackEvent isn't implemented.

Is it planned in future ?

RTCTrackEvent

[hazelduvall]

Hi @ChaitanyaPTank,

We should be supporting the ontrack callback:

node-webrtc/lib/peerconnection.js

Lines 24 to 33 in 3ecdac9

	pc.ontrack = function ontrack(receiver, streams, transceiver) {
	self.dispatchEvent({
	type: "track",
	track: receiver.track,
	receiver: receiver,
	streams: streams,
	transceiver: transceiver,
	target: self,
	});
	};

Though you are correct, this is a native Javascript object as opposed to an Event.

Are there any methods you're using on Event that you need from this? Want to know what motivates this request.

[ChaitanyaPTank]

I am not using this directly but this is used by the SDK I am working with. SDK is doing something with RTCTrackEvent.prototype.

Though I just managed to suppress the error message by mocking

class RTCTrackEvent {
  constructor({ track, streams = [], receiver, transceiver }) {
    this.track = track;
    this.streams = streams;
    this.receiver = receiver;
    this.tranceiver = tranceiver;
  }
}

Not sure if this is perfect or not, works for now.

If it's simple I would like to give a shot. Let me know where to start.

[hazelduvall]

The file I linked above is probably a good place. It has definitions for other events:

node-webrtc/lib/peerconnection.js

Lines 9 to 13 in 3ecdac9

	var RTCDataChannelEvent = require("./datachannelevent");
	var RTCIceCandidate = require("./icecandidate");
	var RTCPeerConnectionIceEvent = require("./rtcpeerconnectioniceevent");
	var RTCPeerConnectionIceErrorEvent = require("./rtcpeerconnectioniceerrorevent");
	var RTCSessionDescription = require("./sessiondescription");

Which indeed are also just Javascript objects. Following their example is preferred. PRs welcome!