This meeting takes place every Friday at 14:00 UTC (currently 7:00am PT, 10:00am ET). 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.

ping:
@Gábor Hojtsy (he/him), @worldlinemine, @lauriii, @Aaron McHale, @anmolgoyal74, @Antoniya, @Ravi, @shaal, @ckrina
Go to the issue of the next meeting to add/remove yourself to/from the list.

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

Transcript of this week's meeting: Drupal Usability Meeting - 2022-04-01.txt

We discussed the following issues:

  • [#TODO]
  • [#TODO]
  • [#TODO]

NR and RTBC issues marked Needs usability review.

Comments

benjifisher created an issue. See original summary.

andregp’s picture

andregp commented
Issue summary: View changes
rkoller’s picture

rkoller
he/him
Primary language German
Location Nürnberg, Germany
commented

We could revisit the topic we briefly touched at the end of todays meeting on the first of april - talk about the research for the dashboard topic. meaning find a consensus about the questions and the wording for the informal questions part as well as the scope and wording for the listening sessions part. more context is provided in the following thread on the drupal slack https://drupal.slack.com/archives/C1AFW2ZPD/p1648219035305469

dww’s picture

dww
we/he/they
commented

#3273009: Improve UX of security coverage status report messages is a very small change that will be a big improvement. The code is ready. Summary is very clear and has screenshots. Should be simple for anyone to review without someone to present.

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

From Slack:

There's a UX question that has come up with testing the CKEditor 5 update (for Drupal 10) during the DevDays: CKE 5 by default uses an autogrow for text areas: starting from just one row and then growing infinetly. Technically, it can be changed to a minimum and maximum height, and it can also roughly change if the sitebuilder changes the number of rows in the form display. Is autogrow a desired functionality? Should it start from just one row? #3273755: CKEditor 5 should not grow to infinite height

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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

rkoller’s picture

rkoller
he/him
Primary language German
Location Nürnberg, Germany
commented
Issue summary: View changes

added the trimmed recording to the issue summary