The JavaScript client library for Sign In With Google and Google One Tap is
designed to be compatible with most common browsers and platforms. It is
not guaranteed to work on all browsers or platforms.
Due to security risks the JavaScript client library is only supported
on the latest two versions of each browser.
Compatibility
Support for the Sign In With Google button and One Tap sign-in flows varies
across browser and platform combinations.
The user experience may differ between browsers based upon availability of
these features:
Supported sign-in flows and features are shown in the following tables. Not all
browsers are available on all platforms, N/A means a supported browser is not
available on the platform.
Sign In With Google
Browser / Platform
|
Android
|
iOS
*
|
macOS
|
Linux
|
Windows 10
|
Chrome
|
|
|
|
|
|
Edge
|
|
|
|
|
|
Firefox
|
|
|
|
|
|
Safari
|
N/A
|
|
|
N/A
|
N/A
|
*
Due to ITP
redirect mode
is required for iOS.
One Tap
Browser / Platform
|
Android
|
iOS
|
macOS
|
Linux
|
Windows 10
|
Chrome
†
|
|
*
|
|
|
|
Edge
*
†
|
|
|
|
|
|
Firefox
*
|
|
|
|
|
|
Safari
|
N/A
|
|
|
N/A
|
N/A
|
*
Extra configuration
is necessary to enable the
upgraded One Tap UX
for browsers that require ITP.
†
FedCM is available in Chrome 117 or later, see
the MDN
Browser compatibility
chart for more information.
Third-party cookies
Privacy Sandbox
for the Web and Chrome's planned
removal of third-party cookies
introduce significant changes to
Google Identity Services (GIS) and user sign in.
As a participant in the W3C
FedID
community group working on
FedCM
,
Google Identity Services has been working to increase user privacy and security
while also minimizing the changes to existing websites and preserving ease of
use for our users. The GIS JavaScript library now supports the proposed FedCM
API.
As of August 2023, Google Identity Services fully supports FedCM and recommends
its use. Changes to
adopt FedCM
may be required for some existing web apps.
Chrome intends to begin
scaled testing
of third-party cookie blocking in
January 2024 with 100% blocking planned by the end of 2024.
Recommended
Not Recommended
As of August 2022, Google Identity Services has conducted a limited
FedCM origin trial
. Approximately 20 websites and 300K users successfully
signed in using FedCM APIs and GIS.
We're pleased to say early feedback has demonstrated that for most websites,
switching to a more private and secure sign-in process without third-party
cookies can occur transparently through backward compatible updates to the
existing GIS library.
Minimal to no changes to existing user flows and
websites was required.
This is a critical point as widespread adoption of
FedCM APIs relies on a trouble-free migration by existing websites.
Based upon this preliminary feedback, GIS plans to expand participation in
testing GIS with FedCM.
During trials these issues were discovered and may require some web sites to
take action when FedCM is adopted by GIS:
- Browser rendered dialogs eliminate the existing ability for sites to use
style attributes or intermediate iframes to control sign-in dialog
positioning. This may obscure existing site content, some of which may be
helpful or critical for users to see before signing in.
- Although not yet widely deployed, some sites may use CSP and COOP.
In these cases, sites may have to make
changes
to direct browsers
to allow popups and to load cross-site resources.