Get an overview of some of the known limitations to the current in-app web browser.
Introduction
The in-app web browser is a powerful tool, but it also has its limitation. In this article we will provide an overview of known limitations.
Audio
When visiting a web page with audio, only the user currently controlling the web browser can hear this audio – all other participants will only see the web page without audio.
The tool we use for the web browser does not provide direct access to a separate audio stream of the web page, so we are unable to send this to all users. Since this is a limitation to a third-party tool we cannot estimate when this might be a possibility.
Video
Video services like Vimeo and Microsoft Streams use the commercial video codec H.264. This codec is not supported in the tool we use for the web browser, so videos hosted on these services cannot be played in the web browser.
Access to peripherals
The web browser does not have access to peripherals like microphone or webcam. This means that even though you can e.g. navigate to the web-version of Teams and join a meeting you can only receive the video stream and audio of other participants – we are not able to send your audio (mic) or video stream (web cam) to the meeting.
Cookies
For security reasons, we do not share cookies across users and sessions. This means that is user#1 logs into a service, and user #2 takes over control of the web browser, user#2 will have to login separately. The same is true is user#1 creates a Space with a web browser where he/she has logged into an online service. If user #2 loads this Space another day, he/she will have to login separately as well.