This helps enable us to use the submit handler more easily as well as make sure we can validate correctly.

Starting on the differentiation between the createUser and addEmail flows.

Make sure the screen does not jump around, add a cancel button.

WSAPI CHANGES in preparation for new UX flows, specifically where you provide a password AFTER verifying emails.

  * stage_user no longer takes a password
  * after calling stage_user, you can poll status with user_creation_status
  * instead of 'prove_email_ownership', you call 'complete_user_creation' and provide a password
  * add_email is now 'stage_email'
  * after calling stage_email, you can poll status with email_addition_status
  * instead of 'prove_email_ownership', you call 'complete_email_addition' and provide a password
  * stage_* and complete_* calls are POST
  * *_status calls succeed continuously (not only once)

Giving the "new email address" field a label.  Made the transition to show the new email address field smoother.

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

issue #276

BrowserIDIdentities has the added advantage of adding the correct classname to the body.

This does no syncing if the user is authenticated.

Changing the signIn button in about.ejs from a button to an anchor.

Since we are autofocusing input elements, it gives a poor user experience because the text flashes.

Conflicts:
	browserid/static/include.js