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

Password error message unstyled #10045

Open
seabelis opened this issue Nov 19, 2024 · 4 comments
Open

Password error message unstyled #10045

seabelis opened this issue Nov 19, 2024 · 4 comments
Assignees
Labels
Affects: Experience Issues relating directly to service design & patrons experience Lead: @rebecca-shoptaw FE: Internationalization, CSS, JS Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Type: Bug Something isn't working. [managed]

Comments

@seabelis
Copy link
Collaborator

Problem

The error message shown to patrons when they've used the incorrect login password blends into the page text and patrons seem to miss it. The error should stand out so it's not missed.

Screenshot 2024-11-19 at 14 09 38

Reproducing the bug

  1. Go to ...login (when logged out)
  2. Do ...use incorrect password to login
  • Expected behavior: Error message should stand out and not blend into text.
  • Actual behavior: Error message blends into text.

Context

  • Browser (Chrome, Safari, Firefox, etc):
  • OS (Windows, Mac, etc):
  • Logged in (Y/N):
  • Environment (prod, dev, local): prod

Breakdown

Requirements Checklist

  • [ ]

Related files

Stakeholders


Instructions for Contributors

  • Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.
@seabelis seabelis added Type: Bug Something isn't working. [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Needs: Lead labels Nov 19, 2024
@seabelis seabelis self-assigned this Nov 19, 2024
@seabelis seabelis added the Affects: Experience Issues relating directly to service design & patrons experience label Nov 19, 2024
@jimchamp
Copy link
Collaborator

#10044 replaces the "Google sign-in is temporarily unavailable[...]" message with the Google sign-in affordance, so things will be like they were before the incident. Is that enough to close this issue, or do you have something else in mind @seabelis?

@mekarpeles mekarpeles added Lead: @rebecca-shoptaw FE: Internationalization, CSS, JS and removed Needs: Lead labels Nov 20, 2024
@mekarpeles
Copy link
Member

@jimchamp I think the problem is actually the lack of emphasis around the error message itself:
Screenshot 2024-11-19 at 9 00 53 PM

I thought maybe we had error message designs from @rebecca-shoptaw's registration redesign w/ Ruijingya

@rebecca-shoptaw
Copy link
Collaborator

We do! The issue seems to be that the error is being sent to the form's "note" div in account.py, whereas the errors in the signup form are added to the i.e. #emailAddrMessage div which lives above the input and has the ol-signup-form__error class.

Just putting that class on would make it look a little strange, and be weird if form.note is used for anything else:
Screenshot 2024-11-20 at 6 34 51 PM

Perhaps a simpler solution would be to add a form.error if submission failed and use that to render the appropriate message in one of those flash-message error divs?

Screenshot 2024-11-20 at 6 38 02 PM

@cdrini
Copy link
Collaborator

cdrini commented Nov 21, 2024

^ That approach makes the most sense, and will also handle the other types of errors login can throw!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects: Experience Issues relating directly to service design & patrons experience Lead: @rebecca-shoptaw FE: Internationalization, CSS, JS Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Type: Bug Something isn't working. [managed]
Projects
None yet
Development

No branches or pull requests

5 participants