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

issue #1582

close #1592

Issue1592

fix bug preventing proper handling of old style verification links by new style code, documented exhaustively in issue #1592.

zero-change cosmetic cleanup of code.  make exit points explicit, and use curly braces consistently.

Fix loadgen

removed extraneous ca.verifyBundle and ca.verifyChain

issue #1592 update complete_email_addition to accept a password in the case that email verification was started on a previous version of the software that didn't collect a password in-dialog

issue #1592 - update complete_user_creation to accept a password in the case that email verification was started on a previous version of code.

Make users who have not yet set their password by time they reach the landing page set their password.

issue #1592

cleanup transitional code for migration from email to userid in stage table

r+ - nice cleanup @lloyd!  Tests run, verified by creating new users and adding users to existing account.

close #1599

Adding timestamp server side to get an intial integration going.

when the server returns a 413 error for posting of interaction data, cle...

Fix for Chrome shifting the "Sign In" button in the email picker when clicking.

when the server returns a 413 error for posting of interaction data, clear the data from local storage - issue #1567

issue #1581

insert a setTimeout between two main phases of assertion generation

closes #1575

insert a setTimeout between two main phases of assertion generation to prevent unresponsive script warnings in IE8 - issue #1575

Partial fix IE6 and IE7 blowing up on main site.  These browsers do not have Array.prototype.indexOf

can now set MYSQL_PASSWORD in env

* css/style.css - where relevant and opacity's are used, use filters for IE6 and IE7.
* shared/storage.js - when clearing localStorage if the user is not authenticated, call removeItem for the emails.  The call to JSON.stringify was blowing up.

issue #1529

Partial fix IE6 and IE7 blowing up on main site.  These browsers do not have Array.prototype.indexOf

issue #1552

@ozten - Nice work on the cleanup.  What if we created one logger that we could use to universally log these sorts of things?  If we consolidated all of the logging into one module, we could add/remove/turn on or off functionality we use for logging.

For the removed "delete" statement, it is safer to use localStorage.removeItem.  I forgot which browser was giving us problems with that, in the end I wrote a load of unit tests and did a browser comparison blog post (http://www.shanetomlinson.com/2012/localstorage-bugs-inconsistent-removeitem-delete/) - the trouble with delete came from IE8.  

In IE8, if the item you are trying to call delete on is not already in localStorage, it will throw an exception.  IE8 does not have this problem with localStorage.removeItem.

r+ - Merging.

close #1546

Replace the removed `delete storage.interactionData` with localStorage.removeItem("interactionData") to avoid IE8 exceptions.