Problem/Motivation

During work on #85494: Use email verification when changing user email addresses and as part of #3263897: Drupal Usability Meeting 2022-02-18, it was identified that because some email templates on the Account Settings form use progressive discovery, it is not always clear that those fields exist.

In the specific case where the checkbox to enable an email template is unchecked the email template body field is not shown. In this case the UI does not make it clear that this additional field exists and that the template can be edited.

If the user wants to change the body of an email template where the corresponding checkbox is unchecked, the user would have to know that the body field exists, and would need to check the box to show the body field, make their changes, then uncheck the box again before saving. This could cause confusion, for example if the user wants to change all of the email templates, but because some body fields may be hidden, they may not know where to go to change those templates.

This behaviour could also be a problem because it creates inequality between changing something via configuration and changing something via the UI. When the user changes the same field via configuration, it doesn't matter whether the box is checked or not, the user can still find and change the field.

Steps to reproduce

Proposed resolution

Remaining tasks

  1. Discuss if this is even something that we should be concerned with.
  2. If so, design a solution.

User interface changes

API changes

Data model changes

Release notes snippet

Comments

AaronMcHale created an issue. See original summary.

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.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.