Following #description_display work defined for elements in issue : #314385: Make position of #description configurable via the API → and what has been done more specifically for fieldsets here #2396145: Option #description_display for form element fieldset is not changing anything → , this issue defines the same work to be done for details type element. Two issue found :
Change template_preprocess_details() in form.inc to include accounting of #description_display element key. Also update the details.html.twig templates to use description_display setting.
NOTE: contrarily to fieldset, the description for details is before by default.
- Review patch and fix.
Description of details elements will now be positionned before or after details content depending of description_display.
None: #description_display should already be part of formAPI regarding #314385: Make position of #description configurable via the API → .
Active
11.0 🔥
forms system
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This came up as daily BSI target
Issue summary could use some love but #129 may be worth exploring?
There may be some cross-over with 🐛 Details elements have incorrect aria-describedby attributes Needs work , which is RTBC.