While migrating from the now deprecated Google Sign-In for Websites to the new Sign In With Google library, I found a bunch of issues which should ideally be routed to the people behind the library, hopefully someone from Google can read this.
- When using JavaScript API, auto_select field seems to have no effect until One Tap is configured: on signing in and page reload no callback is called. Details. This is not at all clear from the documentation reference and deserves a description if this is an intended behavior. Also, even when One Tap is configured, on page reload user sees the One Tap block and the automatic sign-in takes more than 4 seconds in my case. On the contrary, old sign-in button handled page reload duly by calling the callback almost immediately and without any visual representation.
- On the button rendering, there is time (up to ~1 second) when the button is already shown, but it ignores clicks on it. That's not how a new and shiny Sign in With Google button should work, isn't it?
- There does not seem to be a way to provide a hosted domain hint to the user (available in the old library via "hd" field). When only sign-ins from a specific domain are expected and users often have several accounts (e.g. work/personal ones) that was a very useful feature.
- There does not seem to be a way to handle errors on signing in (e.g. wrong client id configuration) - old library provided a JavaScript callback for that and new one just prints messages into JS console.
- Documentation has minor bugs, like links in the Attribute table lead to the sibling "html-reference" page (but should probbaly link to the below sections on the same page) and "Recommended for you" section on the page can link to the now deprecated library.
Any chance these issues can be addressed by improving the library and the documentation?
LinkedIn
Twitter
