added conformance tests.

tests should now pass
updated to jwcrypto that has proper callback delay guarantees and removed unnecessary setTimeouts

Updated all calls to jwcrypto to use the more intuitive API. Fixed a front-end test that was failing due to true asynchronicity of jwcrypto.

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

* 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

* Start with generic Firefox and iOS

issue #1167
issue #1302

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

Using @fawek's pull request as a base for a full solution.

* If the user clicks on the label, proxy the click event to the input element.
* If the user clicks on the input element, let the browser handle things.
* Add user tests to check clicks on both labels and input elements.

issue #1155

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

close #1082

* Change the ordering of the includes so that Function.prototype.bind is declared before gettext.

close #1022

* Pull out core state machine code from the original state_machine.js.
* Update code and tests for use in new state machine.
* Add new state_machine core.
* Add history.
* Add command.
* Update tests.
* Rename resources/state_machine to resources/state

This should simplify a lot of these "cancel email verification" problems.

* Change the ordering of the includes so that Function.prototype.bind is declared before gettext.

close #1022

* Pull out core state machine code from the original state_machine.js.
* Update code and tests for use in new state machine.
* Add new state_machine core.
* Add history.
* Add command.
* Update tests.
* Rename resources/state_machine to resources/state

This should simplify a lot of these "cancel email verification" problems.

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

* Update network to allow for undefined code_version
* Update unit tests.
* Move code_check to static/shared/modules/
* Update build script for new location.

issue #226

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

close #915

Adding i18n to wsapi. Split strings into client.po and messages.po.

Switched email from mustache to EJS templates.

Created fake locale db-LB for development and debugging.

Updated scripts.
See http://viewvc.svn.mozilla.org/vc?view=revision&revision=99911

* Remove the set_password controller, which was never used.
* Remove the set_password test suite.
* Remove the set_password HTML with the autofocus element, which caused some versions of WebKit to wig out.
* In storage.js, make sure when we do JSON.parse, there is something to parse.

close #851
close #889

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

* Add function.prototype.curry
* Make sure all callbacks are called through the "safe" complete function.

close #732

Fixing up a bunch of async problems that were causing the unit tests to error out.  Only call complete whenever jQuery animations are complete.

Upgrading jQuery to 1.7.1.  Fixes a crash bug in IE8 where loading browserid.org would cause IE to restart.

close #806

* All unit tests pass again.
* Renaming primary_user_verified to primary_user_ready
* Adding a random_seed to the context info to fix the unit tests and the adding of the seed.
* Renamed all ejs templates to match their URL.
* Each page unit test writes the ejs template that it needs to the DOM.

* Not actually hooked up in the dialog yet.
* Need backend support.

* Added a new controller, primary_user_provisioned.
* Slimmed down user.provisionPrimaryUser so that it does not authenticate users.
* Using ADD_EMAIL and CREATE_EMAIL as the hash when redirecting back from an IdP as bits of state.

* A lot of cleanup and test adding for handling primary users.
* Trying to genericize a lot of the message names and leave the state machine decide on state.
* Simplifying the ActionsMock in state_machine_unit_test.
* Loads of file renames to make easier to read.

* Hacktastic and minimal tests - loads of tests needed.
* Assume if the #EMAIL=<email> hash is specified on the URL, then try provisioning the user.
* Fixed all previously broken, non-completing tests.
* Added several new controllers - email_chosen, provision_primary_user, verify_primary_user.

* Use WinChan to open a new window to the primary.
* Add the idp_auth_complete page for the IdP to redirect back to.
* When the window closes, re-try to authenticate the user with the primary.
* Add a helper to show an error message.
* Add a WinChan mock.
* Update unit tests to handle the "need to authenticate with IdP" scenario.
* Update compression scripts for WinChan to be included on the main site.

* Match the text on the verify_user page.
* Add a new PageHelper function, replaceFormWithNotice.
* Replacing the specialized code in verify_email_address.js with above function.

* Adding a window Mock.
* Adding a new template for the "you've gotta verify" screen.
* Hooking up the logic to redirect - which closes the window.