How can I have Gallery view AND login at the same time with the Web SDK?

Gallery View requires COOP (Cross Origin Opener Policy) to be “same-origin”.
Login popup requires COOP to be off, otherwise the popup that opens under the domain is not provided the window.opener information that is required for it to confirm the login was successful

How can I have Gallery view AND login at the same time with the Web SDK?

Browser Console Error
If the COOP is set to “same-origin”, the popup will try to send a postMessage to window.opener but there is no opener because the COOP is set to “same-origin”, so this is the error:

TypeError: Cannot read properties of null (reading 'postMessage')
    at a.value (main.js?v=
    at aa (main.js?v=
    at vu (main.js?v=
    at t.unstable_runWithPriority (main.js?v=
    at Yo (main.js?v=
    at du (main.js?v=
    at tu (main.js?v=
    at Qa (main.js?v=
    at Fu (main.js?v=
    at main.js?v=

Which Web Meeting SDK version?
Knowing the version can help us to identify your issue faster. [e.g. 1.9.9]

Meeting SDK Code Snippets
The code snippets that are causing the error / issue so we can reproduce.

To Reproduce(If applicable)
Deploy (important to be deployed) a version of the demo Web SDK with COOP set to “same-origin” and you will be not be able to log into a meeting that requires login.

Demonstration: Loom | Free Screen & Video Recording Software

Device (please complete the following information):

  • Device: Macbook Pro M1 Max
  • OS: macOS 12.0.1
  • Browser: Chrome
  • Browser Version 96.0.4664.110

Greetings, @Felippe,

Thank you for posting on the Developer Forum. For the behavior you are facing, the solution ultimately will be contingent on what’s best for your environment. There are a few approaches you can take into consideration to accomplish your goal. First, have you tried to leverage the same-origin-allow-popups directive? It seems this directive was designed to address the behavior you are experiencing. For context, here is a feature request on the COOP same-origin-allow-popups-plus-coep for reference.



Another approach you can consider implementing is the coi-serviceworker from Github. This recommendation along with several other approaches can also be found in our how to improve performance for the Web Meeting SDK in Chrome and Edge help documentation as well :

Improve performance for the Web Meeting SDK and Web Video SDK in Chrome and Edge.

You may also consider implementing a custom CORS policy provider so you can filter requests on a one-by-one basis.

I hope this helps to clarify your concern.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.