Saad Elbeleidy

@adrienjoly not sure really - you can check if cookies are enabled using [`navigator.cookieEnabled`](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/cookieEnabled) and handle that outside of the component. But I think that will apply to the site...

For this we should also not autovalidate, the default should be to validate on click of one of the buttons and then reflect the errors in the paper-inputs. We can...

I agree that there's a very limited amount of things we can do to deal with this but I also think that the developer and/or end user won't care why...

We should follow [these guidelines](https://firebase.google.com/docs/auth/web/google-signin#handling-account-exists-with-different-credential-errors)

It just seemed like a good idea. That way users can start using your site right away and you can allow them to "upgrade" their account after. The messaging used...

There currently isn't a way to do that. We may potentially fire an event on failed sign in with the error messages but that will likely be in the 1.0...

Yeah this is directly related to #87. I think it's just the failed sign in that we're missing. This is also relevant in social if the user decides to cancel...

Hi @esd100 - thanks for the suggestion. I just noticed this: https://firebase.googleblog.com/2017/02/email-verification-in-firebase-auth.html Maybe there's a way we can incorporate it with the email signup if it's not already automatically incorporated....

We will likely just wait for it to be implemented in polymerfire (https://github.com/firebase/polymerfire/issues/228). Or maybe make a pull request there. I'm thinking in terms of UI we'd have a phone...

Nope. I ended up just switching to using LaTeX.