Making sure the correct buttons are shown when appropriate, smoothing out jumps.

Right now making it its own dialog, not sure if this is correct or not yet.

Only showing the button if the user is actually authenticated.

We want it to look good in Chrome as well!

When hitting enter in a form, the first "input[type=submit]" or "button" is clicked.  We have to make sure the input[type=submit] is the first input element.

close #100

Adding labels, using more semantic markup.

issue #92

Can select buttons using the email address.
Can move through the email addresses and buttons using the tab/arrow keys.

close #86

a re-thinking of forgotten password flow and partial implementation (for the purposes of initial launch, forgotton password flow is a re-verification of email, and it will require re-verification of other emails as well)

reduce the dialog size (and hence its perceived *weight*), and increase the size of some important phrases

add 'this is not me' link to clear localStorage/logout.  add 'addEmailAddress' client flow to associate a new email with your account.

implement localstorage caching of ids and pubkeys, stub out assertion generation crypto and use it from client code