Known Behavior

---

Working around the browsers Autoplay policy

Chrome, Firefox and Safari enforce the Autoplay policy, which blocks automatically playing audio or video. So, we recommend using Web Client SDK only after a user has interacted with your application.

More details on the Autoplay policies are given below

• Chrome Autoplay Policy
• Firefox Autoplay Policy
• Safari Autoplay Policy

Playback of RemoteAudio (audio from other participants) should not be affected in Chrome and Firefox. Safari will pause <audio> elements that playback RemoteAudio, if no local media is being captured or when some other app/tab takes over your camera or mic permissions. They can be played by the application after user interaction.

Note:

To make your integration easier, Web Client SDK follows the following strategy for Autoplay:

• We try to play video every time the stream is changed or updated (E.g.: if other participant mute their video and unmute).
• We try to play video and audio elements (if they are paused) when the page becomes "visible" again after being back-grounded, i.e., when the page comes back to the foreground.
• We try to play video and audio elements (if they are paused) when the user clicks/interacts with the webpage.

However, there are some corner cases where it is not 100% reliable and you might still run into issues specifically on iOS Safari. To reduce the chances of running into these side effects, please ensure that the user interacts with your page at least once before joining the meeting.

Browser extensions and plugins

Some browser extensions and plugins will disable WebRTC APIs, causing Web Client SDK to fail. The following are the plugins that disable WebRTC APIs.

• uBlockOrigin-Extra
• WebRTC Leak Prevent
• Easy WebRTC Block

These are unsupported and likely to break Web Client SDK. If you are having trouble with Web Client SDK, ensure these are not running browsers.

Safari Behavior

Local video permissions are revoked from the current meeting tab on Safari while accessing video controls in a different tab. (E.g. If you open another tab in Safari and ask for video permissions there, Safari takes away camera access from the current tab. The users see the crossed-out camera icon and give access back by clicking on the camera start button. This is expected behavior on the iOS Safari browser.

Support of Beta/Canary/Nightly browser release

We constantly test for and ensure compatibility with the current stable and beta releases of supported browsers. However, because some of the APIs we rely upon, like WebRTC, are under active development in the browsers, we do not guarantee compatibility with Canary or Nightly releases.