The WebRTC API interface RTCTrackEvent
represents the track
event, which is sent when a new MediaStreamTrack
is added to an RTCRtpReceiver
which is part of the RTCPeerConnection
. The target is the RTCPeerConnection
object to which the track is being added.
This event is sent by the WebRTC layer to the web site or application, so you will not typically need to instantiate an RTCTrackEvent
yourself.
RTCTrackEvent()
RTCTrackEvent
object, initialized with properties taken from the specified RTCTrackEventInit
dictionary. You will probably not need to create new track events yourself, since they're typically created by the WebRTC infrastructure and sent to the connection's ontrack
event handler.Since RTCTrackEvent
is based on Event
, its properties are also available.
receiver
Read only
RTCRtpReceiver
used by the track that's been added to the RTCPeerConnection
.streams
Read only Optional
MediaStream
objects, each representing one of the media streams which comprise the track
that was added to the connection. By default, the array is empty.track
Read only
MediaStreamTrack
which has been added to the connection.transceiver
Read only
RTCRtpTransceiver
being used by the new track.There is only one type of track event.
track
The track
event is sent to the RTCPeerConnection
when a new track has been added to the connection. By the time the track
event is delivered to the RTCPeerConnection
's ontrack
handler, the new media has completed its negotiation for a specific RTCRtpReceiver
(which is specified by the receiver
property).
In addition, the MediaStreamTrack
specified by the receiver's track
is the same one specified by the event's track
, and the track has been added to any associated remote MediaStream
objects.
You can add a "track"
event listener to be notified when the new track is available so that you can, for example, attach its media to a <video>
element, using either RTCPeerConnection.addEventListener()
or the ontrack
event handler property.
Note: It may be helpful to keep in mind that you receive the track
event when a new inbound track has been added to your connection, and you call addTrack()
to add a track to the far end of the connection, thereby triggering a track
event on the remote peer.
This simple example creates an event listener for the track
event which sets the srcObject
of the <video>
element with the ID "videobox"
to the first stream in the list passed in the event's streams
array.
peerConnection.addEventListener("track", e => { let videoElement = document.getElementById("videobox"); videoElement.srcObject = e.streams[0]; }, false);
Specification | Status | Comment |
---|---|---|
WebRTC 1.0: Real-time Communication Between Browsers The definition of 'RTCTrackEvent' in that specification. | Candidate Recommendation | Initial specification. |
Desktop | ||||||
---|---|---|---|---|---|---|
Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | |
Basic support | 56 | Yes | 22 | No | 43 | ? |
receiver |
56 | Yes | 22 | No | 43 | ? |
streams |
56 | Yes | 22 | No | 43 | ? |
track |
56 | Yes | 22 | No | 43 | ? |
transceiver |
56 | Yes | 59 | No | 43 | ? |
Mobile | |||||||
---|---|---|---|---|---|---|---|
Android webview | Chrome for Android | Edge Mobile | Firefox for Android | Opera for Android | iOS Safari | Samsung Internet | |
Basic support | 56 | 56 | Yes | 44 | 43 | ? | 6.0 |
receiver |
56 | 56 | Yes | 44 | 43 | ? | 6.0 |
streams |
56 | 56 | Yes | 44 | 43 | ? | 6.0 |
track |
56 | 56 | Yes | 44 | 43 | ? | 6.0 |
transceiver |
56 | 56 | Yes | 59 | 43 | ? | 6.0 |
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/RTCTrackEvent