fix(connect): backport reliable Google WaaS sign-in to v5#607
Merged
Conversation
Deploying web-sdk-react-example with
|
| Latest commit: |
25cb1c2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://35511891.web-sdk-react-example.pages.dev |
| Branch Preview URL: | https://fix-v5-google-waas-button.web-sdk-react-example.pages.dev |
taylanpince
approved these changes
Jul 13, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Ticket link:
API breaking changes:
Manual testing required:
Docs changes required:
Description
Backports the Google WaaS v2 sign-in fix from #606 to Web SDK v5.
Chromium 149+ no longer reliably routes clicks into the hidden, scaled Google iframe used by the previous implementation. This replaces that workaround with Google's directly interactive button for both compact and descriptive layouts.
The core GIS implementation remains aligned with v6, with targeted v5 hardening for React 17 compatibility, responsive resizing, iframe cleanup, and inaccessible loading-state prevention. Social connector layout logic is isolated from the main Connect component.