Comment 5 for bug 1234185

Revision history for this message
Ken VanDine (ken-vandine) wrote :

There are really several issues here that can get users into this situation:
 * The lack of feedback to the user that we are requesting a login page from the provider. When adding an account all you see is a "Cancel" button. The browser-process that gets spawned by signon-ui doesn't show itself until the page is done loading, maybe we should show the webview right away with a loading ActivityIndicator until loading is completed.
 * If you back out and try to add an account again (or cancel and try again), it continues to wait to show the page that was already requested. I've confirmed this by cancelling several attempts and retrying, then killing the browser-process. I then get a login page for the second attempt. Killing that process gives me the third, and so on. So signon-ui is queuing them as it should, but not cancelling when needed.
 * Since we aren't showing anything to the user until the page completes loading, we also don't show any failures to load the page or provide an error handling for that scenario.