disable 'online' check.  too many false positives to be useful.  closes #719 (@shane-tomlinson - I went for a minimal fix given we're branching the beta train right after this commit.  feel free to clean up)

disable 'online' check.  too many false positives to be useful.  closes #719 (@shane-tomlinson - I went for a minimal fix given we're branching the beta train right after this commit.  feel free to clean up)

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

fix issue where when allowPersistent is true, and the user is not authenticated to browserid, they wouldn't be shown the 'keep me signed in' checkbox - closes #776 (presumably a regression introduce in f9ab1ba9 ?)

* Renaming a bunch of the templates to use _ instead of camelCase.

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

* Using address_info right off the start to figure out what to do with an email address.

* Before redirecting to the IdP, shut down all modules, close the channel.
* Update tests to pass from breakages.

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

* Add network.authenticateWithAssertion and related tests.
* On signup page, start the redirection code to verify with primary in new tab.
* in network.js, rename all the onSuccess to onComplete for clarity.
* Simplify tests for primary user provisioning while "not authenticated".
* Generate fake keys/certs in the provisioning mock.
* Save off the keypair/cert given to us by the provisioning frame before getting an assertion.
* Generate an assertion and log the user in on primary provisioning success.

attempt #2 at resolving duplicate ids, rename the new one that's used in fewer places.  fixes frontend unit tests

This reverts commit 3e88cc39.

revived the navigator.id.channel, as well as the #NATIVE and #INTERNAL indications that internal APIs are about to be called

* Adding unit tests for network.addressInfo
* to the XHR mock, adding info needed to test primary/secondary flow.
* Adding a BrowserID.Mock.Provisioning to handle mocking out provisioning capabilities.
* Creating a new User.createUser that handles creating users on either primaryies or secondaries.
* Adding unit tests for the signup page for primary, updating old tests for secondary.
* Starting a shell of error messages and success markup on signup page.
* Starting to hook up the dialog, adding loads of tests.  Secondary based user creation good again.

implement a more generic mechanism to enable local testing and development of primary support - allow SHIMMED_PRIMARIES to be provided which stuffs a auth url, provisioning url, and public key in our cache

implement both sides of the 'provisioning_api' - that which primaries interact with while certifying authenticated users. woo.

partial implementation of trusted side of provisioning setup, enough to try to load primary's provisioning url