This meeting takes place every Friday at 10:00am ET (7:00am PT, currently 15:00 UTC). See Time.is to see what that is in your timezone.

The meetings are held using Zoom, and a link is posted in the #ux Slack channel 10 minutes before the meeting. Agenda is first come, first serve and set by attendees. Use the Needs usability review issue tag for issues that need review and/or suggest issues in comments here.

Recording of this week's meeting: https://youtu.be/yyyo36Aqu7w

We discussed the following issues:

After the meeting, I closed the first as a duplicate of #2579779: Regression: When A Login attempt is unsuccessful two sets of conflicting information are displayed, which I reopened.

NR and RTBC issues marked Needs usability review.

Comments

benjifisher created an issue. See original summary.

mrpauldriver’s picture

mrpauldriver commented

Please could I spotlight a core bug which can result is in a poor user experience following a failed log in attempt.

#3179666: Inline Form Errors module advises that a failed login attempt with the wrong password is because of providing the wrong username.

benjifisher credited AaronMcHale.

benjifisher credited ckrina.

benjifisher credited worldlinemine.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Issue summary: View changes
benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Issue summary: View changes
Status: Active » Fixed
benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Issue summary: View changes
Related issues: +#2579779: Regression: When A Login attempt is unsuccessful two sets of conflicting information are displayed, +#3067273: Provide form for customizable settings, +#2803187: Allow book navigation title to be overridden by top-level node title
benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented

I added this comment to #2579779: Regression: When A Login attempt is unsuccessful two sets of conflicting information are displayed, but maybe it is better to add it here:

We identified two problems with notifications that we might want to address, but not as part of this issue:

  1. Drupal puts all status messages in the same place (usually at the top of the screen). This is appropriate for site errors, but it is confusing to put user errors in the same place.
  2. The problem in this issue is similar to one we discussed in #2895055: Edit the date range error messages. With the login form and with datetime rage fields, there are two related fields. There is no way to decide which one has the invalid input, but the IEF module picks one. (I think it picks the first one on the form.) This can be confusing.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.