This repository has been archived by the owner. It is now read-only.

(dev/next-train) dialog 'forgot password' screen missing some context about which email #1580

Closed
jrgm opened this Issue May 11, 2012 · 6 comments

Comments

Projects
None yet
5 participants
Member

jrgm commented May 11, 2012

STR:

  1. go to http://myfavoritebeer.org/ or http://dev.myfavoritebeer.org/, and click 'Sign in'
  2. enter an email secondary address that is previously known to (browserid.org|dev.diresworb.org)
  3. when you get prompted for a password, click 'forgot password'
  4. Here's the difference. In prod 'reset password' shows the email address that will be reset; in dev, it lacks that context (perhaps this is intended, but it just struck me as curious).

In prod:
img

In dev:
img

Agreed, we need a short bit of copy that says this is a password reset

Member

jrgm commented May 11, 2012

Actually, I was thinking that showing the email address (as it was before) would be good (what email address am I resetting).

Member

jrgm commented May 11, 2012

Actually, sorry, yeah, you're right. Both copy and what email should be there.

@ghost ghost assigned billder May 15, 2012

billder commented May 21, 2012

The tricky thing here is overly associating a specific email address with the password. I'd like for people to associate the password with Persona, and not with one specific email address.

shane-tomlinson added a commit that referenced this issue May 24, 2012

Make the in dialog set-password flow work with requiredEmail.
* In set_password.ejs, only show the "cancel" button if not setting the initial password for a required email.
* Update required_email.js to handle the set-password in dialog flow.
* Clean up required_email.js so that it is easier to follow.
* Rename the "add_email_submit_with_secondary" message to "stage_email" - much clearer.
* Show a message whenever resetting the account password.

issue #1638
issue #1580
Member

shane-tomlinson commented Jun 30, 2012

closed by issue #1889.

Contributor

jbonacci commented Aug 13, 2012

Verifying as covered by fixes for #1889 which is already closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.