While working on implementing Google+ Sign-In's hybrid / one-time auth code flow, I encountered an error in Chrome's JS console. The error occurs after the sign-in prompts and granting permission to the app, specifically when Google's code attempts to call back to the button:
Uncaught SecurityError: Blocked a frame with origin "https://ww2.fa.org" from accessing a frame with origin "https://accounts.google.com". Protocols, domains, and ports must match.
This issue does not seem to arise in Safari or IE. It also occasionally happens in Firefox but is more frequently reproducible in Chrome. Refreshing the frame with the sign-in button (after following Google-side prompts) often results in the refreshed button acknowledging that the sign-in was successful and calls the success handler. Ideally, it should work without needing a refresh, yet it consistently requires one.
Any insights? The sign-in can be accessed at . It only requests the email scope if you'd like to investigate further!