"Your account was created successfully" page has silly form fields
Bug #1015514 reported by
Matthew Paul Thomas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
Fix Released
|
Low
|
Unassigned |
Bug Description
1. Go to <https:/
2. Go to <https:/
3. Finish creating an SSO account.
What you see:
a. The message "Your account was created successfully."
b. A menu for "Preferred email (?)"
c. A "Manage email addresses" link.
d. "Choose password" and "Retype password" fields.
What you should see:
b. No menu, because your account can't possibly have more than one e-mail address yet.
c. An "Add another e-mail address" link, perhaps.
d. No password fields, because you only just chose your password a few minutes ago.
Changed in canonical-identity-provider: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
OK, something that should address these concerns without being hard to implement (I think):
If the user has only one email address, the form should show "Email address" and show the address only (i.e. not in a field since it's not editable here).
If the user has more than one email address, then we do show the dropdown to allow selection of the preferred address. This will be committed when "save changes" is pressed.
I don't have a problem with the "manage email addresses" link but potentially, if there's only one e-mail address, this could become "add email address". Since we don't allow editing or removing the preferred (or only, if there's just one) address, this wouldn't be confusing. One can only manage (which does involve deletion) when there's more than one address.
Also, the "choose password/re-type password" fields could be "hidden". A "change password" link would expand the hidden element. That way the fields aren't just there staring at the user: a link prompting specific action would be present. There's some coding involved to ensure that if the user entered bad password data, the next reload of the form shows these fields "expanded" again, to avoid confusion (huh,