Latest Chrome Extension breaks Google Sign-In on our website?

Hi @tklevenz , my name is Hilary and I'm the software developer that implemented the"block competing popup" feature. I can see how this change has caused some end users the inability to login to some of their normal sites, and that your signups have also been negatively affected. I'm sorry that blocking popups has had this negative consequence.

To speak to the implementation, what 1Password does is stop network requests to https://accounts.google.com/gsi/status* which is accomplished through the native declarativeNetRequest API. I made this implementation decision because it has the same behaviour as toggling this setting in google:

Users can turn off pop-ups this way, without 1Password, so I believed following google's approach would have the least negative impact. We knew some people would be affected and in retrospect, we could have done more to:
1. Notify site maintainers ahead of time so that they can update their website.
2. Notify users of this change so they can turn the 1Password toggle on/off.

In terms of a solution for sites like vecteezy, they will have to use Google's recommended button for authentication that steph_giles shared above. Lot's of websites rely on Google authentication and we definitely want to keep that experience positive.

Other than vecteezy, I can't find another site encountering an issue logging in with Google, but if anyone here knows of some, I'd be happy to reach out to them to help.

I'm also open to answer any technical questions about this feature, and will share product feedback with my manager.