Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Real-Time Validation to Account Registration Form #2055

Closed
4 tasks done
Tracked by #7694
mekarpeles opened this issue Apr 16, 2019 · 3 comments
Closed
4 tasks done
Tracked by #7694

Add Real-Time Validation to Account Registration Form #2055

mekarpeles opened this issue Apr 16, 2019 · 3 comments
Assignees
Labels
Affects: UI Issues with the web site's user interface. [managed] Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Needs: Response Issues which require feedback from lead Primary Focus The active main quest of this contributor Priority: 2 Important, as time permits. [managed] registration Type: Epic A feature or refactor that is big enough to require subissues. [managed] Type: Subtask of Epic A subtask that is part of the work breakdown of an epic issue (see comments). [managed] validation

Comments

@mekarpeles
Copy link
Member

mekarpeles commented Apr 16, 2019

Dependency to epic #7694

Considerations

UX side note: don't show negative feedback while a user is typing (don’t debounce during typing, instead show after e.g. tab out / defocus)

Requirements

Is your feature request related to a problem? Please describe.

Add real-time, client-side validation for email, username, and password to the account registration form.

Describe the solution you'd like

User should see feedback that:

  • Email is unavailable on IA/OL
  • Username is already taken on IA/OL
  • Email, username and/or password is incorrectly formatted

Proposal & Constraints

Please try to use existing components as much as possible (minimize css changes)

@mekarpeles mekarpeles added accounts registration Type: Subtask of Epic A subtask that is part of the work breakdown of an epic issue (see comments). [managed] validation labels Apr 16, 2019
@mekarpeles mekarpeles added the Priority: 1 Do this week, receiving emails, time sensitive, . [managed] label Apr 23, 2019
@brad2014 brad2014 added Affects: UI Issues with the web site's user interface. [managed] and removed ui labels May 13, 2019
@xayhewalo
Copy link
Collaborator

Labeling this backlogged since it doesn't look like it's been worked on since May. Let me know your thoughts @mekarpeles

@mekarpeles mekarpeles added Priority: 2 Important, as time permits. [managed] and removed Priority: 1 Do this week, receiving emails, time sensitive, . [managed] labels Oct 30, 2019
@mekarpeles mekarpeles added the Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] label Dec 17, 2019
@mekarpeles mekarpeles reopened this Apr 17, 2024
@mekarpeles mekarpeles added this to the Sprint 2024-05 milestone Apr 17, 2024
@mekarpeles mekarpeles added the Lead: @rebecca-shoptaw FE: Internationalization, CSS, JS label Apr 26, 2024
@mekarpeles mekarpeles added Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] and removed Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] Lead: @rebecca-shoptaw FE: Internationalization, CSS, JS labels Apr 26, 2024
@rebecca-shoptaw
Copy link
Collaborator

👍🚀

@rebecca-shoptaw
Copy link
Collaborator

rebecca-shoptaw commented Apr 29, 2024

Status update!

It's been great working on this project today, and I've got a good amount of progress to report so far.

For the sake of simplicity, I'll make and keep updating a checklist re: what we would like the form to do here:

Required form behavior / tasks

Other Requirements

  • We need to communicate that screen name is public
    • Already done, if a little inelegantly
  • Clicking submit/pressing enter, any empty fields will be highlighted red, and the error text next to the field will say “This field is required”
    • Fixed in main project branch via built-in HTML required attribute

Fun possibilities

  • Generate username suggestions using whatever function appends digits in the backend
  • Add keyup checks to remove error message as soon as the input is fixed (but not apply the error message on key up, see UX side-note in original issue)
  • Disable submit button until all inputs are entered
  • Do some kind of animation then check mark or x to indicate whether username is available (a very common and nice thing in forms)
  • Move some formatting checks out of the backend

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects: UI Issues with the web site's user interface. [managed] Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Needs: Response Issues which require feedback from lead Primary Focus The active main quest of this contributor Priority: 2 Important, as time permits. [managed] registration Type: Epic A feature or refactor that is big enough to require subissues. [managed] Type: Subtask of Epic A subtask that is part of the work breakdown of an epic issue (see comments). [managed] validation
Projects
None yet
Development

No branches or pull requests

5 participants