Version 21.2.0
What's new in this release?
- API for pinning a participant's video
- The new PinParticipant API enables you to pin a participant's video.
- The syntax for this new API is:
- PinParticipant({participant:Object, pin:Boolean})
Resolved issues
The following table lists the issues we have resolved in VidyoClient for WebRTC JavaScript Library Version 21.2.0.
|
VidyoClient for WebRTC JavaScript Library Version 21.2.0 - resolved issues |
|
|---|---|
|
Key |
Summary |
|
IOWEBRTC-1920 |
When using Chrome Canary 91, the participants list now properly displays the list of participants. |
|
IOWEBRTC-1919 |
If a speaker is plugged in or unplugged while using Chrome on a Mac, the selected speaker no longer displays as "None"; instead, the correctly selected speaker is displayed. |
|
IOWEBRTC-1915 |
The preview tile no longer gets overlapped by the right pane. |
|
IOWEBRTC-1910 |
If a user does not allow permission to use the microphone, that user can now still hear the other users in the call. |
|
IOWEBRTC-1909 |
The timestamp inside the chat bubbles now remains within the border of the bubbles. |
|
IOWEBRTC-1905 |
The names of the participants in the Participants tab now display fully across the field. |
|
IOWEBRTC-1868 |
The requested resolution no longer changes when the loudest speaker switches. |
|
IOWEBRTC-1682 |
Video tiles are now correctly displayed in one row instead of two rows. |
|
IOWEBRTC-1214 |
If a call participant shares content in a very narrow window, other users joining that call are now able to see the shared content. |
|
IOWEBRTC-1142 |
On WebRTC calls, the video tiles no longer randomly change their layout when there is a mobile user in portrait mode on the call. |
Known issues
The following table lists the known issues in VidyoClient for WebRTC JavaScript Library Version 21.2.0.
|
VidyoClient for WebRTC JavaScript Library Version 21.2.0 - known issues |
|
|---|---|
|
Key |
Summary |
|
IOWEBRTC-1999 |
If a participant in a call is pinned using the PinParticipant API, and another participant mutes their camera, the tile of the muted participant is also displayed. |
|
IOWEBRTC-1983 |
When using a Pixel 4 XL on Android 11, the Chrome tab may freeze when a remote participant hangs up and rejoins the call a few times. |
|
IOWEBRTC-1942 |
Because of known limitation on iOS (iPad OS), if a call participant on an iPad uses the back camera for video and the front camera for camera sharing, the iPad user will see their self-view tile as black and the other call participants will see a black tile from the iPad user. |
|
IOWEBRTC-1921 |
Video tiles that drop from calls due to network conditions sometimes do not get restored when the network conditions improve. |
|
IOWEBRTC-1906 |
If a call participant with more than one camera or microphone disconnects their active device while their camera/microphone drop-down list is open, the drop-down list doesn't update to display the remaining camera/microphone. |
|
IOWEBRTC-1861 |
When using iOS 14, audio artifacts can be heard for a few seconds after the remote participant starts speaking. |
|
IOWEBRTC-1860 |
When using Safari Technology Preview 121 on a Mac with an Intel processor, users are unable to share content. This is a known issue with Safari that cannot be fixed by Enghouse Vidyo at this time. |
|
IOWEBRTC-1804 |
Audio lip-sync is delayed on WebRTC after VidyoConnect is put in the background and then returned to the foreground. |
|
IOWEBRTC-1784 |
Audio lip-sync is delayed on iOS Safari after flipping the camera, muting and unmuting, or putting VidyoConnect in the background. This is a known issue with Safari that cannot be fixed by Enghouse Vidyo at this time. |
|
IOWEBRTC-1705 |
Occasionally, Chrome encodes at 10-15 fps even when the network is unconstrained. |
|
IOWEBRTC-1673 |
On Macs with dual-core CPUs, when the "Google Chrome Helper (Renderer)" process goes beyond 100% CPU, Chrome detects a CPU limitation and lowers the encoding resolution. |