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

It's extremely disappointing that 1password deliberately block google's functionalities that greatly benefit the customers, just to promote their own features. I hope that 1Password makes better choices.

Was just investigating Google One-Tap not working in our application when I stumbled on this thread. I understand that 1password wants to offer a unified way of signing in when on a sign in screen. However this breaking the One-Tap functionality without any alternatives is rough. One-Tap is a large factor in driving signups on our website, so I have to agree with the previous commenters, extremely disappointing, especially when we just switched from lastpass to 1password company wide, just a few weeks ago.
I feel like the "Disable Stop competing sign-in popups in the browser" option should be opt in, but as a developer I do understand why you are not doing that, however I also have to question your implementation here.

Thanks to @nicedawg for posting... I was going crazy trying to log into my Vecteezy account to check billing details... two days of trying. Even before I realized you were with Vecteezy, it dawned on me to just try a different browser (which worked). Then I confirmed that turning off 1PW in Chrome allowed me to sign in with my Google account. Sadly, clicking on Vecteezy's "Log in with Google" just sits forever and never gave any feedback. Thanks for clearing up the what, if not the why!

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.

twobird.com is another one

Thank you for sharing this @carydubek, I have passed it on to the team.

ref: dev/core/core#21437

Thanks for sharing @carydubek!

I did a little investigation and it looks like even with 1Password uninstalled I can't signup to twobird.com. I checked my google settings and they look good, but I receive this error:

To address the ongoing issue with Google's FedCM, developers must include the data-use_fedcm_for_prompt="true" tag into their OneTap HTML code. This implementation will eliminate the necessity to adjust 1Password settings, ensuring site visitors remain unaffected.

https://developers.google.com/identity/gsi/web/guides/fedcm-migration