* Remove the signup page and all remnants of it.

* If the user enters an unknown secondary email, redirect them to the /signup page.
* If the user arrives with a known secondary email in storage, show the password field.

When a secondary email is verified, make sure its verified bit is set to true.  Lots of cleanup for readability.

* Generalize and cleanup unit tests

* Still focus the first address if no address is selected.
* Show a tooltip if the user has not selected an email address.
* Adding test helper functions to test for element focus and check.

new KPIs in the event stream:
* authenticate.enter_password
* authenticate.password_submitted
* authenticate.password_success
* authenticate.password_fail

Added a couple of new testHelper functions, expectedMessage and unexpectedMessage

* 'number_emails'
* 'sites_signed_in'
* 'sites_visited'
* 'orphaned'
* 'new_account'
* 'email_type'

issue #1667
issue #1730

* Only show info once the account has been verified.
* Unify the styles for the "has this address already been registered" error.
* Remove all the dead code that was left over from issue #1000 merge.

issue #1734

* Reduce the number of places where the TOS/PP agreements are shown.
* Commenting the holes in coverage for required_email.

Show the BrowserID and RP TOS/PP at the correct time with the correct text.

* BID TOS/PP is only displayed to new users.
* RP TOS/PP is only displayed to new users, or users who have not been to a site before.

Details:
* Bring over rp_info.js from another branch. Module charged with displaying RP related info.
* In authenticate, add_email, and pick_email controllers, trigger message to update "next" button text to be correct for the particular screen.
* To dom-jquery, add hide and show functions.

Call controllers that need to display the TOS/PP info with siteTOSPP parameter.  This reduces the amount of data that needs to be passed around.

issue #1240

Change browserid.org urls to persona.org, introduce static.login.persona.org for all static resources.

* network.js - add cookiesEnabledOverride, a flag that forces the cookie status for testing.
* testHelpers.js - add testUndefined and testNotUndefined.
* user.js - fix documentation. in checkAuthentication, if the user is not authenticated, call the callback with false instead of undefined.

* Add tests to make sure all expected fields are present.

issue #1660

* Add the startExternalDependencies option when initializing the dialog controller, if set to false, no external dependencies are loaded.  Used for testing.
* Add a new test to check for script containing emails.
* Add unit tests for tosURL and privacyURL.
* Add a testHelpers.testErrorNotVisible
* Removed the actions.js->doError and its tests, it is no longer used.

* Removed the .interactionData namespace from storage.js, created our first model - shared/models/interaction_data.js
* Simplified how data is stored into interaction_data, created current and staged sub-namespaces
* Added stageCurrent and publishStaged functions.
* in shared/modules/interaction_data.js, simplified calls to model.
* Tried to make the xhr mock make more sense and provide facilities usable for peeking at last XHR request data.

issue #1597

Other notable changes:
* Send old interaction data irregardless of whether the current dialog session is collecting data.
* Because of this above change, simplified storage regarding data.
* Make sure when sampling is enabled, data is saved.
* Make sure when sampling is disabled, data is not saved.
* Added tests to test expected flow.

* user.js: Update verifyEmail and verifyUser to take a password.
* network.js: Update completeEmailRegistration and completeUserRegistration to take a password.
* Replace verify_email_address.js and add_email_address.js with a single verify_secondary_address.js to reduce duplication.
* Update the templates.
* Bring back verify_email_address and add_email_address templates, but remove the verify password field.
* To dom-jquery, add show, hide functions.

* 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.

* 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.

Adding more tests to make sure when the user sets a password, the min/max password lengths are checked.

* to testHelpers, add a generateString function which generates a string of the specified length.
* Replace the manual creation of strings for long passwords with generateString.
* To verify_email_address_test, adding checks for min and max length when setting the password.

issue #1173

The problem stemmed from the DOM was not completely reset between every test.  When the manage page inserted email addresses into its portion of the DOM, it added email addresses with elements with the same ID as the pick email controller.  Instead of ensuring we clean wipe these elements between every test, rely on QUnit's ability to reset a portion of the DOM to its initial state.

* Add the `qunit-fixture` class to the bit of DOM that should be reset between every test run.
* Add the testHelpers.setup/testHelpers.teardown functions to several suites that manually called emtpy() on DOM elements.

issue #1156

When clicking "use another email address" after "reset password", send user back to authentication screen.

* Update the state machine to have a doResetPassword.
* If cancelling and the next state is doResetPassword, go back two steps to auth screen.
* When going to auth screen, print original email address.

issue #984

When clicking "use another email address" after "reset password", send user back to authentication screen.

* Update the state machine to have a doResetPassword.
* If cancelling and the next state is doResetPassword, go back two steps to auth screen.
* When going to auth screen, print original email address.

issue #984

* Put all tests under the cases directory.
* Remove the extraneous _unit_test on the end of every file name.
* Put qunit related code into qunit.
* Put mocks and testHelpers into top level test directory.

Adding the shell of a cookie check.  Cleaning up network.js, changing network.js's callbacks to be simpler.

* Adding complete to helpers.js, which required a reordering of scripts.
* Using complete in network.js so that existence of callbacks is checked automatically.
* Add a cookie_check.js module which checks which shows an error message if the user's cookies are disabled.
* Get rid of yesterday's code which triggered an event if cookies were disabled.

issue #835.

* Makes for easier debugging and testing.

* Add new delay screen.
* Add new tests to check for delay screen.
* Simplify display logic of the error message.

close #915

* The xhr_delay module would take away the wait screen as soon as any XHR message was complete, even if no xhr requests were delayed.

close #913

* Add the "xhr_disable_form" module - whenever there is an XHR request, it greys out all buttons.
* Fix the tests that were borked yesterday.

issue #905
issue #888

* Moving /static/dialog/controllers/page.js to static/shared/modules/page_module.js
* Adding /static/shared/modules/xhr_delay.js
* Updating tests.
* Updating compress script.
* Update includes list.
* Make the error/wait screens display using CSS transitions.

issue #905

* If the user is not authenticated to "password" authentication when they select a secondary email, make them sign in.
* Updaate required_email to do its own check for the user's authentication status.
* Update the unit tests to make sure we are all kosher.

* Update network/user to handle two level auth.
* Update tests that check authentication status to check for correct status.
* State machine checks for the correct authentication level for an email address.

* Simplify the signature for checkAuthenticationAndSync by removing onSuccess.
* Simplify the user unit tests by using failureCheck.
* Add testHelpers.failureCheck which came from network.js
* Cleanup the user unit tests a ton.

* Added tests for the various flows in required_email.
* cache off address information, clean up required_email controller a bit.
* Add some error messages.
* User.addressInfo now returns whether the primary users are authenticated with their IdP.

Required email feels more "correct", still some work to do though for working with expired certs cleanly.

* Changed the state machine so pushing a state to the stack is optional.
* Changed the verify_primary_user screen to have an optional cancel button
* Updated required_email to handle primary verification of unauthenticated users.