This is a followup to #1953568: Make the bundle settings for entity reference fields more visible. → .
In #1953568: Make the bundle settings for entity reference fields more visible. → , we struggled with fulfilling all three of these principles:
The elephant in the room is the spacy and quite obtrusive "Help text" field. We considered moving it further down, together with the "required field" setting:
but abandoned this approach because of principle 2 (generic ones first).
Instead I'm proposing to wrap the help text element in another details element, unless it is actually used. Finally, most of the time a description or help text isn't needed as field label and/or widget clearly convey what is meant to be entered.
Needs work
10.1 ✨
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
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.
The change alters the user interface, so before and after screenshots should be added to document the UI change. Make sure to capture the relevant region only. Use a tool such as Aviary on Windows or Skitch on Mac OS X.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
Seems like a nice little feature to add
Tagging for tests to verify the markup for help text appears in the details.
Tagging for usability review as this is a UI change
Tagging for before/after screenshots.
Thanks!