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

implementation of interaction data collection

upgraded to new jwcrypto API, including backend, frontend, and tests.

merge latest dev into upgrade-jwcrypto branch, porting fixes to verifier's support of delegation of authority to new jwcrypto apis

Reusing checkSupport to implement delegatesAuthority in lib/primary. 

update the http_forward module to allow global request timeouts to be set, use this to implement a 15s upper bound on requests for declaration of support in development.  This should fix unit tests

Start the verifyEmailAddress page controller even if there is no token.

Consolidating exception logging, removing delete which can cause problems in Chrome. [Partially?] Fixes Issue#1546

Updating documentation in cookiesEnabled to include Android 4.0 default browser still passing the cookiesEnabled check with cookiesDisabled.

close #1542

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.

Ensure the cookies disabled check does not run on /tos, /about or /privacy

Fix the global variable introduced and other JSHint errors.

Renaming kpi_backend_db_hostname and port to kpi_backend_db_url. Updated with KPIggybank endpoint, posting form data

* If the controller's "continuation" option is specified, start saving data immediately to localStorage.
* in start.js, look for CREATE_EMAIL and ADD_EMAIL on the window.location.hash. If this exists, the dialog session is a continuation.
* Add some more tests.

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.

To test:
* Make sure verification works if a valid token is given.
* Make sure error message is displayed if invalid token is given.
* Make sure error message is displayed if no token is given.

issue #1495

* Create a list of pages where the cookie check should be run.

issue #1514

issue #1521

unbreak auto-deployed dev by updating deployment image - previous had a database pre-created which is no good when we change the schema.