* Use blanket as the coverage reporter.
* Install `grunt-blanket-mocha` to handle reporting results to grunt.
* Set up new grunt task, `grunt coverage` for reporting.
* Add more front end tests where coverage was lacking.
* Hook up code coverage results to the intern by running tests in PhantomJS
* Only enable code coverage if explicitly requested
* Only enable front end tests in dev mode.
* Fix code that gave PhantomJS problems (Function.prototype.bind)
* Add consolidate middleware to handle the interface between express and handlebars
* Add a middleware to respond to 404s
* Add a branch to the 't' handlebars helper to deal with 't' when invoked in templates written using res.render
* Update grunt tasks to manage dist mode server rendered templates.
BREAKING CHANGE:
The production configuration script must add a new option to its config :
```
page_template_subdirectory: 'dist'
```
issue #554
.
* Allow users who sign up with an existing account to sign in. If they type an incorrect password, show them a link to the /signin page.
* Show users who sign in with a non-existent account a link to the /signup page.
* Clarify & simplify error processing of errors returned by the auth server
* Add a table of human understandable string types->numeric codes returned by the auth server to auth-errors.js
* All access to auth-errors goes through three functions, toMessage, toCode, and is;
* Add displayErrorUnsafe - no conversion on HTML before being displayed.
* Add functional tests for /signin and /signup error cases.
* Focus can only be checked for if the window is currently in focus.
* .error is used by mocha to indicate errors. Namespace all checks for .error to the view.
* Up time timeout for mocha to 5seconds and the intern to 120seconds.
* Add a unit test for signing in with a non-existent user (see https://github.com/mozilla/fxa-js-client/issues/74)
fixes#489
* Save forceAuth to the session. If forceAuth is set, only show back button in the reset_password screen.
* Reset the forceAuth flag from sign_in and sign_up
* Add reset password resend to the fxa-client wrapper.
* Rename requestPasswordReset to passwordReset - update consumers.
* Add visual feedback when email is resent.
* Add BaseView.preventDefaultThen to reduce event handling boilerplate. BaseView.preventDefault returns a proxy event handler that backbone can use to call event.preventDefault, then another handler.
fixes#272
* Update the /settings screen with change password and sign out functionality
* Add /delete_account
* Add new auth-server functions to the fxa-client
* Allow the fxa-client to handle updating the Session state
* When visiting /, redirect to /signup
issue #254
* Use a session cookie to keep track of whether the user is too young.
* If the user revisits the signup page after being booted out for being too young, ship them back to the "cannot_create_account" page.
* Update the text on the Cannot Create Account screen to go along with @jgruen's new mocks and legal's feedback.
issue #226
* Add a placeholders for password reset flow in FxA Client wrapper.
* Add a new file "url.js" which contains "searchParam"
* Move several common functions to base.js (isElementValid, displayError)
issue #121
* Add mocha & chai to the bower config.
* Add a functional test shell for the confirm screen.
* Go to the correct page on startup if the browser supports Fx events.
* Mocha tests now run as part of the intern functional tests.
* Fetch the code, uid, and service from the URL search string.
* Handle errors
* In the create_account screen, only attempt to create an account if both email and password are available.
* rename tests/functional/signIn.js => sign_in.js and signUp.js => sign_up.js for consistency.
* Update bower config to fetch the new FxA JS client.
* In postinstall npm command, install the FxA JS client's dependencies and do a build so the client is available.
* Create a light wrapper around the FxaJSClient to reduce boilerplate code.
* Use the fxa-js-client from the bower install, get rid of picl-gherkin