Checking for incorrect password takes like 4 seconds

[Avi Romanoff]

To reproduce:

1. Go to the log-in screen
2. Type an incorrect password for your account.

Nothing will happen, the UI will not freeze, but 3-5 seconds later the log in box will bounce indicating an incorrect password.

This is a problem because if you hit "return" multiple times, you will need to wait like 12 seconds before being able to type a new password in.

[Raphael Isemann (teemperor)]

Yeah, i removed the spinning thing from the avatar as it looks ultra-ugly without no white background (as in the old greeter). I assign to the UX team and let's see what they want as visual feedback.

[Danielle Foré (danrabbit)]

Go here: http://daneden.github.io/animate.css/ and select "shake". I think this is a good animation because it has parallels with shaking ones head (which, afaik is pretty universal for "no").

Removing the spinner was a good call, we don't need that.

I think the idea behind blocking the UI was a security feature so that it's harder to manually bruteforce the password. But instead of a spinner, we can just use a slightly longer animation. I believe on animate.css they're using a 1s animation which is pretty long without feeling annoying.