Important Change That May Affect Your Customers
Google Chrome is considered a very secure browser. To further improve its security, inline installation of the screensharing extension for Chrome is being deprecated. The timeline provided by Google is as follows:
- "Starting September 12, 2018, inline installation will be disabled for existing extensions, and users will be automatically redirected to the Chrome Web Store to complete the installation."
- "In early December 2018, the inline install API method will be removed from Chrome 71."
- "In late January 2019, extension-free screenshare on Chrome will officially be available with the release of Chrome 72. If you are still on Chrome 71 and below, an extension will be required to screenshare."
Google is working on implementing the getDisplayMedia() approach for screensharing in Chrome so an extension won't be needed. We suggest you read these pages to learn more about the changes:
- Intent to implement from Chrome
- Chrome bug tracking the feature
- Chrome platform status on the feature
- The getDisplayMedia() API will be released in Chrome 72.
- Users that already have the screenshare plugin installed will not be affected by updating to Chrome 71.
What Does This Mean to My Customers?
For Google Chrome versions 70 and older, if you do nothing to update your own app, your new customers will still be redirected to the Chrome Web Store to install your screensharing extension via the inline installation method. As a result, they will be navigated to the Chrome Web Store to download and install your screensharing extension before they can share their screen.
With the release of Google Chrome 71, support for inline installation of screensharing plugin has been removed. For the last few months prior to this, end users were able to download the screensharing plugin in the Chrome Web Store via Chrome's inline installation function. However with Chrome 71, this method will no longer work. To work around this, you will need to update your application to explicitly launch the Chrome Web Store when an end user wants to install the screensharing plugin. For more information regarding this change, you can look at the following Chrome article:
TokBox has updated its JS SDK to support Chrome's v72 implementation of getDisplayMedia() and thus obviate the need for an extension. To maintain a good user experience, you'll want to leverage changes to the TokBox SDK to support an effective, friction-free UX.
We highly recommend that you update your app to use the latest version of the OpenTok JS SDK since we are planning to support Chrome's implementation of getDisplayMedia(). By using at least v2.15 of our OpenTok JS SDK, your app will automatically use getDisplayMedia() when Chrome 72 is released, providing a seamless experience when switching to extension-free screensharing.
What TokBox Will Do
We have implemented the getDisplayMedia() API in anticipation of Chrome's support for extension-free screensharing.
We intend to continue sharing what we're doing to update our platform, what you can do, and what you should do to prepare your business. We will update our JS SDK to support Chrome's implementation. We're evaluating the need to patch existing JS SDKs. We'll communicate changes through this page, our blog, and email.
What Can You Do?
Here are a few things you can do:
- Familiarize yourself with proposed changes using the links above about Google's intention.
- Subscribe to changes on this page as we provide more information, sample code, and guidance.