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.

Comments

Cottser created an issue. See original summary.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.