Add option use_fedcm_for_prompt with same value than oneTapEnabled #755
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
So will this be implemented anytime soon? |
|
2nd a desire to implement this |
|
Please implement this feature asap 🙏 |
This was referenced Sep 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Developers will be migrated by default starting April 2024. Opt-in to FedCM (set boolean flag to true) to test and make any necessary changes to ensure a smooth transition.
Developers using Automatic Sign-in feature should migrate to FedCM as soon as possible to reduce any potential impact on conversion rates.
If you need more time to verify FedCM functions properly on your site and make changes to your code, set the boolean flag to false. This will temporarily exempt your traffic from using FedCM. Regardless of the flag selection, starting on January 4, 2024, users that are part of Chrome’s Tracking Protection rollout will have limited access to third-party cookies, and unless FedCM is enabled, One Tap and Automatic sign-in will not be displayed to these users.
Reviewing the required changes:https://developers.google.com/identity/gsi/web/guides/fedcm-migration#migrate_your_web_app
I think that we will need at least a new property on https://developers.google.com/identity/gsi/web/reference/js-reference#IdConfiguration
I have used same value that for oneTapEnabled as both options are related