AI-generated Key Takeaways
-
With the migration of One Tap to the FedCM API, browsers will control the prompt's size and position, eliminating support for custom positions.
-
Developers are advised against customizing the position for new One Tap integrations and to review the migration guide for existing integrations to ensure compatibility.
-
Customizing the One Tap login flow is possible, including positioning the prompt within a container element by utilizing the
data-prompt_parent_id
attribute, but avoid obscuring any prompt content to comply with Google's policies. -
Remember that the
data-prompt_parent_id
attribute is disregarded on mobile web browsers, limiting customization in those environments. -
Hiding or manipulating the One Tap prompt's content to misrepresent its origin from a Google iframe can lead to severe consequences, including project or account suspension.
By default, the One Tap prompt is displayed in the top-right corner of desktop web browser windows. When FedCM is used, browser fully controls the prompt location. Hence, custom layouts are not supported.
Otherwise, display One Tap inside a container element to change prompt position.
To do so, specify the DOM ID of the container element in the
data-prompt_parent_id
attribute.
The following code example reuses the g_id_onload
element as the container
element and displays the One Tap prompt in the specified position:
<div id="g_id_onload"
data-client_id="YOUR_GOOGLE_CLIENT_ID"
data-login_uri="https://your.domain/your_login_endpoint"
data-prompt_parent_id="g_id_onload"
style="position: absolute; top: 100px; right: 30px;
width: 0; height: 0; z-index: 1001;">
</div>
The data-prompt_parent_id
attribute is ignored on mobile web browsers.