I encountered an issue with this element when opening a page in the background (e.g., middle-click on a link). At this point, Polymer sets enough properties to kick off the AuthEngine initialization and login workflow, but Polymer hasn't actually attached all of its elements yet, so elements that are bound via Polymer to that event don't actually receive it.
I was able to fix this by hooking Polymer's ready event instead of its attached event here.
The code that ultimately results in the events being fired iterates through the
signinAwareslist, which is the list of<google-auth-signin-aware>elements that have been attached at that point.I encountered an issue with this element when opening a page in the background (e.g., middle-click on a link). At this point, Polymer sets enough properties to kick off the
AuthEngineinitialization and login workflow, but Polymer hasn't actually attached all of its elements yet, so elements that are bound via Polymer to that event don't actually receive it.I was able to fix this by hooking Polymer's
readyevent instead of itsattachedevent here.