- Issue created by @benjifisher
- ๐ฌ๐งUnited Kingdom AaronMcHale Edinburgh, Scotland
The group is actively tracking progress on:
Issues brought forward from the previous meeting:
- โจ [Meta] Appearance page is too long and confusing Active
-
๐
[PP-3] Figure out what to do with the install/uninstall modules page
Postponed
with notes:
- #3307567: Drupal Usability Meeting 2022-09-09 โ : started discussing the proposed options but ran out of time, possibly splitting the confirm form into its own issue (we may want to look at that for both modules and themes, standard pattern, consider implications of project browser), worth considering parity with Drush (and other extension/package managers).
- #3310096: Drupal Usability Meeting 2022-09-23 โ : @simohell presented the various proposals, but we again ran out of time to have a in-depth discussion, using the drop-button pattern on the module page for the existing links + Uninstall was suggested.
-
๐
Placement of batch progress messages
Active
with notes:
- #3322499: Drupal Usability Meeting 2022-11-25 โ : We started looking at the issue but ran out of time.
-
โจ
Allow media items to be edited in a modal when using the field widget
Postponed
with notes:
- @AaronMcHale: Issue could use some guidance.
In comment #109 the issue was marked as postponed for needing input from UX, accessibility and media initiative. Apparently there are some outstanding UX/accessibility questions (but I'm not sure what they are). This was echoed in comment #111.
Comment #144 is asking what is needed to move the issue along (the postponed state seems to be causing some delays/confusion as to how to proceed).
Perhaps we can at least take a look at what the issue is doing and provide some recommendations/guidance on how it could be implemented.
- @AaronMcHale: Issue could use some guidance.
- โจ Allow blocks to be configured to show/hide on 200/403/404 response pages Fixed : see comment #3335028-6: Drupal Usability Meeting 2023-01-27 โ for more details on what a review should address.
- ๐ Password suggestions are hidden from screenreaders Active
-
๐ฑ
[Policy] Remove tour module from core
Fixed
with notes:
- @xjm tagged for review and sign off from the usability group before it can go ahead, noting that Tour is seen as a usability module and the core committers were not able to reach a consensus.
- ๐ Creating a new workspace should also switch to it Needs work
- โจ Provide Drupal root path on file system admin form Needs work
- ๐ Improve search settings help text Fixed
- ๐ Add image preload option to help boost actual and perceived performance Needs work
- ๐ UX: Hide entity ID in autocomplete widget Needs work
-
๐
Wrong message on cancelling account with e-mail confirmation request
Needs work
with notes:
- Reviewed at #3244123: Drupal Usability Meeting 2021-10-22 โ and we made a recommendation (in comment #13), but there was a good point made in comment #17 so in #18 I tagged it again for review.
- โจ Allow hiding configured blocks in layout builder Needs work
- โจ Add visibility control conditions to blocks within Layout Builder Needs work
- ๐บ๐ธUnited States BlackBamboo Washington DC
benjifisher โ credited BlackBamboo โ .
- ๐ฉ๐ชGermany rkoller Nรผrnberg, Germany
benjifisher โ credited rkoller โ .
- Status changed to Needs work
over 1 year ago 3:24pm 2 June 2023 - ๐ฉ๐ชGermany rkoller Nรผrnberg, Germany
Left a comment on the project browser issue: #3323354-19: Review all pop-up messages shown by the Svelte UI installer for user friendliness โ
- Status changed to Fixed
over 1 year ago 2:18am 15 June 2023 - ๐บ๐ธUnited States benjifisher Boston area
I am adding a link to the recording and a rough transcript. I already assigned issue credit, and @rkoller commented on the issue we spent most of the time on.
Looking at โจ Allow blocks to be configured to show/hide on 200/403/404 response pages Fixed , I think we can leave it alone. Usability review was requested in #70, provided in #72 (after ๐ Drupal Usability Meeting 2020-06-23 Closed: outdated ) and added back with no comment in #158. I think that @smustgrave is right to remove it again (#179).
We can declare this issue finished.
Automatically closed - issue fixed for 2 weeks with no activity.