We have some confirm forms that are more destructive than others. For example, the module uninstall confirm form can result in deleting large numbers of configuration entities, dropping database tables etc..
This came up whilst reviewing a new feature to delete content entities prior to uninstallation of a module where it was suggested that we swap the buttons and mark the delete all button as a danger button. See #2688945-90: Allow removing a module's content entities prior to module uninstallation → . Eventually we decided not to do that because of UX concerns.
Some proposed designs so far have included one or more of these elements:
Review the design.
None
http://127.0.0.1:8888/admin/modules/uninstall/confirm
→
http://127.0.0.1:8888/admin/appearance
Uninstalling a theme displays no warning even though all of the theme's blocks are deleted.
http://127.0.0.1:8888/node/16/delete
→
http://127.0.0.1:8888/block/1/delete
→
http://127.0.0.1:8888/admin/structure/block/manage/umami_search/delete
→
http://127.0.0.1:8888/node/BID/delete
→
http://127.0.0.1:8888/node/NID/delete
→
http://127.0.0.1:8888/comment/COMMENT_ID/delete
→
http://127.0.0.1:8888/admin/structure/contact/manage/feedback/delete
→
http://127.0.0.1:8888/admin/structure/types/manage/article/delete
→
http://127.0.0.1:8888/admin/structure/types/manage/article/fields/node.a...
→
http://127.0.0.1:8888/admin/config/media/image-styles/manage/large/delete
→
http://127.0.0.1:8888/admin/structure/media/manage/audio/delete
→
http://127.0.0.1:8888/media/1/deletee
→
http://127.0.0.1:8888/admin/structure/menu/manage/example/delete
→
http://127.0.0.1:8888/admin/structure/menu/item/1/delete
→
http://127.0.0.1:8888/admin/config/regional/language/delete/es
→
http://127.0.0.1:8888/admin/structure/taxonomy/manage/recipe_category/de...
→
http://127.0.0.1:8888/taxonomy/term/27/delete
→
http://127.0.0.1:8888/admin/config/content/formats/manage/basic_html/dis...
→
http://127.0.0.1:8888/user/2/cancel
→
http://127.0.0.1:8888/admin/people/roles/manage/administrator/delete
→
http://127.0.0.1:8888/admin/structure/views/view/articles_aside/delete
→
Active
11.0 🔥
Last updated
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
A list of the concerned pages should be included:
The Basic page content type is being used 8 times on your site. You may not remove this content type until you have removed all of the Basic page content first.
Page 1
Page 2
Page 3
Page 4
Page 5
Page 6
Page 7
Page 8