Cross origin isolation is a new security feature enforced from Chrome version 92 onwards which is scheduled to release on 20th July 2021. The cross-origin isolation will now be required on web pages using powerful features such as SharedArrayBuffer that are performance-critical.
This feature release is critical for our Zoom WordPress plugin users. It implies that the Zoom Web SDK used by our plugin will not be able to function properly if cross-origin is not enforced for the Zoom meeting view. Here is the official announcement by Zoom in this regard. The Zoom meeting features that are tested to fail without complying with this security update are the Share Video and Gallery View feature on the embedded Zoom meeting page.
The great news is that the compatibility for this change has already been released in our v4.16.0 update of the Zoom WordPress plugin on July 13, 2021.
All you need to do is to update the plugin to this version to avoid any troubles for the users accessing the plugin after July 20th with the Chrome v92 release.
The plugin v4.16.0 update might create some issues on your Zoom meeting page only for certain use cases. The below points address these issues that could show up on the Zoom Meeting embed page ONLY IF you are:
- Loading resources on that page from a site other than your current site domain.
- embedding URLs from a cross-domain or even your own site.
Your domain: https://examplesite.com
These errors could show up in Chrome Dev Console.
1) Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep
2) Specify a Cross-Origin Embedder Policy to prevent this frame from being blocked
3) Specify a Cross-Origin Resource Policy to prevent a resource from being blocked
Caution: Technical knowledge will be needed to address points #2 & 3
Are you facing any other issues after the update? Comment below so we can address that too!