Cross-Origin-Opener-Policy policy would block the window.closed call.

[allenfuller]

I am experiencing an issue completing the oAuth account process. After confirming the oAuth connection via a service, the pop-up closes, but the link is not added. I have 6 entries in the console for:

oauth_browser.js:25 Cross-Origin-Opener-Policy policy would block the window.closed call.

Has anyone else experienced this issue?

It appears there's an issue with `` in the util package (Meteor issue #11363), but I don't know where to add the WebApp.connectHandlers.use. Would that be in a startup file?

Thanks for any advice!

[github-actions]

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee you issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know

[allenfuller]

Update: This bug happens specifically with Google, however in general the popup does not close after confirming the connection.

[allenfuller]

Actually, it appears this whole thing is related to Meteor oAuth, or even Chrome, so I'm closing this one. However, if anyone has dealt with the popup not closing, I'd love your feedback.

[StorytellerCZ]

Yes, this is potentially a Meteor bug if you have too strict content policy. Best to open an issue on the Meteor repo to see if we can find a workaround.