Consider using <details> in "Available translation updates" report

Created on 17 July 2016, over 8 years ago
Updated 24 May 2024, 6 months ago

Problem/Motivation

Steps to see this:

  1. Enable the language and interface translation modules
  2. Add at least one other language
  3. Navigate to /admin/reports/translations

The page looks fairly similar to /admin/modules overall but doesn't make use of the <details> element, instead adding its own custom JS for expanding/collapsing in locale.admin.js.

After briefly searching through #1804702: Display interface translation status โ†’ it seems like <details> wasn't really used in core when this form was created.

Proposed resolution

Instead of using custom markup and JS, use <details> to hold the additional translation information.

Remaining tasks

  • Decide if this is a good idea
  • Decide where we can apply this - only to the locale module? Also to Classy/Stable?
  • Write a patch

User interface changes

Slightly different UI - currently the UI breaks RTL conventions for example.

API changes

TBD

Data model changes

Not likely.

๐Ÿ“Œ Task
Status

Needs work

Version

11.0 ๐Ÿ”ฅ

Component
Localeย  โ†’

Last updated 3 days ago

Created by

๐Ÿ‡จ๐Ÿ‡ฆCanada star-szr

Live updates comments and jobs are added and updated live.
  • CSS

    It involves the content or handling of Cascading Style Sheets.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024