Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
3 years agoLatest Chrome Extension breaks Google Sign-In on our website?
Hello,
We run a website that uses https://developers.google.com/identity/gsi/web/guides/overview, and recently started noticing problems logging into our own website via Google (and then of course...
steph_giles
1Password Team
3 years agoHey all,
Just a little more information on this one.
To prevent confusion with our 'Sign in with' feature and to help user's know which provider they use to sign in on a site, the latest version of 1Password in the browser includes a feature which prevents Google's One Tap UI from appearing. The One Tap UI is intended as an addition to the traditional "Sign in with Google" button.
On testing some sites where we are seeing the problem described above it appears that the "Sign in with Google" button is a custom button that is intended to present the One Tap UI.
Google shares this on their page:
Warning: The One Tap UI should be displayed automatically on page load or other window events, instead of being triggered by a user gesture. Otherwise, you may get a broken UX. Users may not see any UI after a user gesture, due to globally opt-out, cool-down, or no Google session, etc.
If a user isn’t signed into a Google account in their browser, or if they have turned off “Google Account sign-in prompts” in their account settings, the button will not work.
We recommend using Google's Sign in With button which follows Google's guidelines, creates a better user experience, and is not affected by our new feature and the troubles you have described.
I hope this helps!
Edit: typo