* For the buttons, use id's instead of classes.
* Focus the "yes" button when the screen is shown.

issue #1582

issue #1581

* If the controller's "continuation" option is specified, start saving data immediately to localStorage.
* in start.js, look for CREATE_EMAIL and ADD_EMAIL on the window.location.hash. If this exists, the dialog session is a continuation.
* Add some more tests.

don't require that a user re-enter their password in dialog after email verification in a different browser.  Because the user just typed their password, attempt to authenticate them in the verification originating browser via the API.  If that works, then automatically log them in

* Move #thisIsNotMe button handler from the page_module to pick_email.
* Remove extra tests for the authenticate controller.
* use the alias for BrowserID.User in helpers.js
* Add password fields to the forgot page.

* helpers.addEmail triggers either "primary_user" or "add_email_submit_with_secondary"
* Add states to the stage machine to handle add_email_submit_with_secondary to either set a password or stage the user.
* Add two helper functions in storage.js, addPrimaryEmail and addSecondaryEmail

* Verify the user without checking for passwords on the verification pages.
* Update /wsapi/stage_email to take a password.
* Remove the password fields of the verify page forms.
* Set the password when adding an email address.

* Remove the forgot_password controller, templates, tests, etc.
* Update authenticate to trigger "new_user" with rehydration info
* Update set_password to be able to handle resetting passwords as well.
* Update the state machine to handle password setting or resetting.

* Update set password to handle either initial password set or a password reset
* Update network/user.js to handle passwords when creating new users or resetting passwords.

* This fixes a problem where it is possible that a user takes more than 2 minutes to answer, making the already generated assertion invalid.
* A lot of general cleanup of the state machine.
* Push all post email selection flows to a new state, "email_valid_and_ready" which decides whether to ask the user the computer ownership status.
* Assertions are generated after the "is this your computer" is asked.
* doEmailChosen is replaced with doGenerateAssertion - there were multiple calls to generate an assertion, not very DRY.
* Fix a problem in network.js where a user who completes user registration should be marked as authenticated.
* rename email_chosen.js to generate_assertion.js to clarify its purpose.

issue #1460

issue #1508

issue #1496

Generalize fix by adding to fixupURL.  fixupURL is used to clean all URLs that come from outside the dialog.

issue #1446

Fix primary email being set as most recently used if the user cancels redirect to authenticate with primary.

issue #968

* A little bit of cleanup to simplify the check_registration controller - there is only a back button now.
* In the ejs template, remove the href and id attributes from the strings passed to localizers. Always use back for the id.
* Add a test to make sure the correct messages are triggered whenever pressing the back button.

issue #1453

Update to @lloyd's pull request 1447 to ensure that cancel from required email verification still works.

* A bit of code cleanup in required_email.js to remove the extra "cancel" message that was never called.

pull request 1447

* Fix the password not being displayed if a user must auth on account validation.
* Fix the assertion not being immediately generated if user does not need to auth.

issue #1440

Place the entire "If you're at a public computer such as a library or internet cafe, we'll ask you..." on a single line.

This should fix the l10n extraction tools cutting the string off.

issue #1425

* Secondary links all are some shade of dark grey/black with a dotted underline.
* Change the font used on the "about" page to be the standard Helvetica Neue except for the header.
* Change the style of link in the TOS/PP to black text with a dotted underline.
* Loads more link updates!
* A lot of cleanup to remove duplicate `color: #549fdc` entries by using the action class.
* On the main site, put the action links to the far left of the main button.
* Reduce the amount of "forgot password" CSS by generalizing.
* Generalize the yellow banner on the main site.

issue #702

A bunch of changes to make the design more responsive to all screen sizes - mobile, desktop and tablet.

* Start with a slight refactor of the CSS and DOM.
* Vertical center content when content is smaller than the screen size.
* Constrain email addresses and show ellipsis if emails overflow box width.  Make sure width is updated when browser window size changes or user changes the screen direction of their device.
* If form/email address list is taller than available form area, show scroll bar on desktop or expand contents so that entire app must be scrolled on mobile.
* If dialog opened on a tablet or large desktop window, add a gradient to the left size of the white area that matches the gradient on the arrow.
* On mobile, footer should always be at the very bottom of the screen unless contents overflow screen height, where it will be pushed off the bottom of the screen.

Things to test and be aware of:
* Dialog should respond to various screen sizes when resizing browser window on desktop.
* IE8 does not support media queries so narrowing the browser window will not force the dialog into "mobile" mode.
* Contents in the "form area", wait, delay, or error screens should always be vertically centered.
* IE6/IE7 should still see the unsupported dialog with the correct layout (untested on checkin due to #1390)
* Wide emails should always be constrained to the screen width on mobile or box width on desktop.  The layout should respond to changes in device orientation.
* The box surrounding the emails should show a scroll bar on desktop/tablet if there are more emails the available screen height.  On mobile, the entire screen height should expand so that the entire app must be scrolled.
* On mobile, the footer should always be at the very bottom of the screen unless the form area takes up more vertical space than the device height.

issue #1101
issue #1317

issue #1402

repair internal.get API - it should return a bare assertion represented as a string, not an object - issue #1395

* add network.prolongSession
* add user.setComputerOwnershipStatus and user.isUsersComputer. setComputerOwnershipSTatus calls network.prolongSession if called with true.
* in controllers/is_this_your_computer, call user.setComputerOwnershipStatus

issue #1349

* Clean up the way the other hints are hidden and shown.

issue #1290

* Adding a "setUserMustConfirmComputer" function to storage. This forces the user to confirm whether the computer is theirs.  Used for testing.

* Fix the tests that had to do with the assertion_generated.
* Update the XHR mock to pass back the userid on authentication.
* Do the closing animation just before the dialog is actually ready to close.

* state.js - rename "publish" to "redirectToState", rename "gotoState" to "startAction" and "subscribe" to "handleState" for clarity.
* state.js - do the "is this your computer" check from "assertion_generated" so that it is taken care of for all types of assertions (primary, secondary, required).

* Add a unit test harness for is_this_your_computer
* When the user authenticates, set them as seen.
* In storage.js, Use an object to store the usersComputer info instead of arrays for developer grok.
* Add storage.js->clearUsersComputerOwnershipStatus for testing.
* Clean up user.js->logout a little bit.
* Completely clear localStorage between every test.
* Add tests to check for when the user should see the "is this your computer" screen.

rework how we decide when to ask about computer ownership: no is sticky for 24 hours.  only ask if it's been 1 minute since we first saw the user (not on the first login).  also defend against garbage in localstorage.