[null,null,["最后更新时间 (UTC)：2025-08-06。"],[[["\u003cp\u003eThe JavaScript client library for Sign In With Google and Google One Tap supports the latest two versions of Chrome, Edge, Firefox, and Safari on varying platforms.\u003c/p\u003e\n"],["\u003cp\u003eSign In With Google and One Tap have differing support across browsers and platforms, with ITP requiring redirect mode for iOS and extra configuration needed for the upgraded One Tap UX on ITP browsers.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Identity Services recommends enabling FedCM for new web apps and migrating existing apps to enhance user privacy and security by minimizing reliance on third-party cookies.\u003c/p\u003e\n"],["\u003cp\u003eWhile FedCM adoption generally requires minimal website changes, some sites might need adjustments for sign-in dialog positioning and CSP/COOP configurations.\u003c/p\u003e\n"],["\u003cp\u003eFor devices with limited input capabilities or lacking system browsers, specialized sign-in guidance is available in the provided documentation link.\u003c/p\u003e\n"]]],[],null,["# Supported browsers and platforms\n\n| **Important note:** For apps running on devices that don't support a system browser or that have limited input capabilities, such as TVs, game consoles, cameras, or printers, see [Sign-In on TVs and\n| Limited Input Devices](/identity/gsi/web/guides/devices).\n| **Note:** Android and iOS webviews are not supported for user sign-in. We recommend using [Chrome Custom Tabs](https://developer.chrome.com/docs/android/custom-tabs/) on Android and [SFSafariViewController](https://developer.apple.com/documentation/safariservices/sfsafariviewcontroller) on iOS instead. For more information on security best practices, see [Use secure browsers](/identity/protocols/oauth2/resources/best-practices#use-secure-browsers).\n\nThe JavaScript client library for Sign In With Google and Google One Tap is\ndesigned to be compatible with most common browsers and platforms. It is\nnot guaranteed to work on all browsers or platforms.\n\nDue to security risks the JavaScript client library is only supported\non the latest two versions of each browser.\n\nCompatibility\n-------------\n\nSupport for the Sign In With Google button and One Tap sign-in flows varies\nacross browser and platform combinations.\n\nThe user experience may differ between browsers based upon availability of\nthese features:\n\n- [Intelligent Tracking Prevention](https://webkit.org/blog/9521/intelligent-tracking-prevention-2-3/) (ITP)\n- [Federated Credentials Management API](/privacy-sandbox/3pcd/fedcm) (FedCM)\n\nSupported sign-in flows and features are shown in the following tables. Not all\nbrowsers are available on all platforms, N/A means a supported browser is not\navailable on the platform.\n\n### Sign In With Google\n\n| Browser / Platform | Android | iOS ^\\*^ | macOS | Linux | Windows 10 |\n| Chrome | | | | | |\n| Edge | | | | | |\n| Firefox | | | | | |\n| Safari | N/A | | | N/A | N/A |\n|--------------------|---------|----------|-------|-------|------------|\n\n^\\*^ Due to ITP [redirect mode](/identity/gsi/web/guides/display-button#redirect_mode) is required for iOS.\n\n### One Tap\n\n| Browser / Platform | Android | iOS | macOS | Linux | Windows 10 |\n| Chrome ^†^ | | ^\\*^ | | | |\n| Edge ^\\*^ ^†^ | | | | | |\n| Firefox ^\\*^ | | | | | |\n| Safari | N/A | | | N/A | N/A |\n|--------------------|---------|------|-------|-------|------------|\n\n^\\*^ [Extra configuration](/identity/gsi/web/guides/itp) is necessary to enable the\n[upgraded One Tap UX](/identity/gsi/web/guides/features#upgraded_ux_on_itp_browsers) for browsers that require ITP.\n\n^†^ FedCM is available in Chrome 117 or later, see\nthe MDN [Browser compatibility](https://developer.mozilla.org/en-US/docs/Web/API/FedCM_API#browser_compatibility) chart for more information.\n\nThird-party cookies\n-------------------\n\nAs a participant in the W3C [FedID](https://www.w3.org/community/fed-id/) community group working on [FedCM](/privacy-sandbox/3pcd/fedcm),\nGoogle Identity Services has been working to increase user privacy and security\nwhile also minimizing the changes to existing websites and preserving ease of\nuse for our users. The GIS JavaScript library now supports the proposed FedCM\nAPI.\n\nAs of August 2023, Google Identity Services fully supports FedCM and recommends\nits use. Changes to [adopt FedCM](/identity/gsi/web/guides/fedcm-migration) may be required for some existing web apps.\n| **Important:** When testing sign-in and third-party cookie blocking, you should start by updating to the latest stable version of Chrome.\n\nRecommended\n\n- [Enable FedCM](/identity/gsi/web/reference/js-reference#use_fedcm_for_prompt) for new web apps and [migrate](/identity/gsi/web/guides/fedcm-migration) existing apps.\n\nNot Recommended\n\n- Disabling FedCM.\n\nAs of August 2022, Google Identity Services has conducted a limited\n[FedCM origin trial](https://developer.chrome.com/blog/fedcm-origin-trial/). Approximately 20 websites and 300K users successfully\nsigned in using FedCM APIs and GIS.\n\nWe're pleased to say early feedback has demonstrated that for most websites,\nswitching to a more private and secure sign-in process without third-party\ncookies can occur transparently through backward compatible updates to the\nexisting GIS library. **Minimal to no changes to existing user flows and\nwebsites was required.** This is a critical point as widespread adoption of\nFedCM APIs relies on a trouble-free migration by existing websites.\n\nBased upon this preliminary feedback, GIS plans to expand participation in\ntesting GIS with FedCM.\n\nDuring trials these issues were discovered and may require some web sites to\ntake action when FedCM is adopted by GIS:\n\n- 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.\n- Although not yet widely deployed, some sites may use CSP and COOP. In these cases, sites may have to make [changes](/identity/gsi/web/guides/get-google-api-clientid#content_security_policy) to direct browsers to allow popups and to load cross-site resources."]]
