Releases: twilio/twilio-video.js
2.0.0-beta4
2.0.0-beta4 (November 29, 2018)
Bug Fixes
- Fixed a bug where, when a Safari Participant joins a Room after a Firefox Participant,
it did not receive video frames for VideoTracks published by the Firefox Participant. (JSDK-2224)
2.0.0-beta3
2.0.0-beta3 (November 20, 2018)
Bug Fixes
- Fixed a bug where unpublishing a LocalTrack from within one of its event
listeners that have been added before publishing it to the Room throws a
TypeError. (JSDK-2212)
Note for Electron developers
- twilio-video.js will no longer be usable on Electron 2.x or below. Please
upgrade to Electron 3.x or higher.
1.14.1
1.14.1 (October 10, 2018)
Bug Fixes
- Fixed a bug where twilio-video.js was internally using the deprecated RemoteTrack's
id
property. (JSDK-2173)
2.0.0-beta2
2.0.0-beta2 (October 1, 2018)
Bug Fixes
- Fixed a bug where calling a LocalVideoTrack's
stop
method did not stop the
video capture, and thereby did not turn the camera light off. (JSDK-2156) - Fixed a bug where calling LocalParticipant's
unpublishTrack
on a LocalTrack
that was being published to a Room also stopped the LocalTrack. (JSDK-2169)
1.14.0
1.14.0 (August 28, 2018)
New Features
- Added a new property to ConnectOptions,
dominantSpeaker
, for enabling the
Dominant Speaker API. Once the Dominant Speaker API is generally available,
you will need to set thedominantSpeaker
property totrue
. This will only
take effect in Group Rooms. - Added a new property to ConnectOptions,
networkQuality
, for enabling the
Network Quality API. Once the Network Quality API is generally available,
you will need to set thenetworkQuality
property totrue
. This will only
take effect in Group Rooms.
For example, here is how you can enable both APIs:
connect(token, {
dominantSpeaker: true,
networkQuality: true
});
Please note that these features are still in beta and not generally available.
Bug Fixes
- Fixed a bug where we erroneously raised deprecation warnings for "trackAdded"
and "trackRemoved" events. (JSDK-2131) - Reduced our usage of MediaStreams in Firefox. This should improve performance.
(JSDK-2118) - Worked around Firefox Bug 1481335.
- Fixed a bug in our workaround for WebRTC
Issue 8329.
2.0.0-beta1
2.0.0-beta1 (August 10, 2018)
Breaking Changes
- RemoteParticipant no longer emits the deprecated "trackAdded" and "trackRemoved"
events. Use the "trackSubscribed" and "trackUnsubscribed" events instead. - LocalParticipant no longer contains the deprecated
addTrack
,addTracks
,
removeTrack
andremoveTracks
methods. UsepublishTrack
,publishTracks
,
unpublishTrack
, andunpublishTracks
instead. - RemoteTrack no longer has the deprecated
id
property. Use thesid
orname
properties instead. - RemoteTrack no longer has the deprecated
isSubscribed
property. Use the
corresponding RemoteTrackPublication'sisSubscribed
property instead. - RemoteTrack no longer emits the deprecated "unsubscribed" event. Use the
corresponding RemoteTrackPublication's "unsubscribed" event instead. - Participant's
trackPublications
collection is now renamed totracks
.
Similarly,audioTrackPublications
is now renamed toaudioTracks
,
dataTrackPublications
is now renamed todataTracks
, and
videoTrackPublications
is now renamed tovideoTracks
. Participant no
longer maintains the deprecated Track-based collections. - We removed support for Bower.
1.13.1
1.13.0
1.13.0 (July 30, 2018)
New Features
-
When the Room is completed via the REST API, the Room emits a "disconnected"
event with a TwilioError 53188, "Room completed". Previously, there was no way
to distinguish this case from callingdisconnect
on the Room (JSDK-1884). In
some applications, this will be expected, so you should set an event listener
on the Room as follows:room.once('disconnected', (room, error) => { if (!error) { console.log('You disconnected from the Room by calling `disconnect`'); return; } switch (error.code) { case 53118: console.log('The Room was completed server-side'); break; // Handle any other errors of interest. default: console.error(`You were disconnected: ${error.message}`); break; } });
1.12.0
1.12.0 (July 25, 2018)
Deprecations
The following 1.x
APIs/events are now deprecated and scheduled for removal
in [email protected]
:
- Participant's "trackAdded" and "trackRemoved" events
- RemoteTrack's
id
property - RemoteTrack's
isSubscribed
property - RemoteTrack's "unsubscribed" event
Please refer to the migration guide below for handling these deprecations.
Bug Fixes
- Fixed a bug where publishing a LocalVideoTrack with VP8 simulcast enabled
caused Chrome to crash. (JSDK-2032) - Fixed a bug where we used deprecated
getStats
APIs in Firefox. (JSDK-1227)
Migration Guide
Migrating from Participant's "trackAdded" and "trackRemoved" events
-
On the LocalParticipant, these events indicated that a LocalTrack has been
scheduled to be added to or removed from a Room. Since calling
publishTrack
orunpublishTrack
conveys the same information, we have
deprecated these events. -
On the RemoteParticipant, you can use "trackSubscribed" and "trackUnsubscribed"
events as drop-in replacements:participant.on('trackSubscribed', track => { console.log(`Subscribed to a RemoteTrack: ${track}`); }); participant.on('trackUnsubscribed', track => { console.log(`Unsubscribed from a RemoteTrack: ${track}`); });
Migrating from RemoteTrack's deprecated properties and events
-
Instead of the RemoteTrack's
id
property, use itssid
orname
property. -
Instead of the RemoteTrack's
isSubscribed
property, use the corresponding
RemoteTrackPublication'sisSubscribed
property. -
Instead of listening to the RemoteTrack's "unsubscribed" event, listen to
the corresponding RemoteTrackPublication's "unsubscribed" event:publication.on('unsubscribed', track => { console.log(`Unsubscribed from a RemoteTrack: ${track}`); });
1.11.1
1.11.1 (July 3, 2018)
This release simply updates the dependency on @twilio/webrtc.