* Remove the signup page and all remnants of it.

Generalize error-display to extended-info.  For every "screen" that is shown, create an extendedInfo and instantiate it.  Remove the "error-display.show" code that was in page_helpers and page_module.

issue #1916

* Add a new module called dom-helpers with function makeEqualWidth.
* Force buttons on the "Is this your computer" screen to be the same width.
* Update CSS enable button width to be set this way.
* Update CSS to vertically center helper text.
* Update CSS to make the buttons look good in mobile.

issue #1932

common/
      js
      css
      i

dialog/
      js
      css
      i

pages/
      js
      css
      i

* Make the about code use a PageModule.
* Include the about module in the static_resources instead of including it separately.
* Start the about module when looking at the about page.
* Add ultra basic unit test for about page.

* Add a new controller and template - rp_info
* Adjust the screen size hacks to take into account the dynamic height "favicon"
* Add an action to start the rp_info service.

* properly check and escape logoURL and name in dialog.js
* Add some tests ensuring logoURL and name are escaped.
* Print information in rp_info controller.

issue #1098

A lot of cleanup to make the site smoother, IE8 fixes, removing dead code, make the arrow transition smoother.

* On the main page, update card with new design.
* Simplify a lot of styles and layout.
* Clean up the "about page"
* Using css transitions for the arrow slide.
* Change all BrowserID text to Persona.
* Fix a problem on the main site where the footer would was not at the bottom in Webkit and Opera browsers.
* Fix the background color or IE8 in the signUpForm and congrats messages.
* When signing in to the main site, use a tooltip instead of error message on incorrect password.

* 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

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