Add "changed" hints to translation settings page

Created on 29 November 2012, over 11 years ago
Updated 29 May 2023, about 1 year ago

Follow up for #1810386: Create workflow to setup multilingual for entity types, bundles and fields β†’

Problem/Motivation

The new workflow for translation settings on bundles is great. But could be improved to communicate what the site builder has changed while working on the page.

Proposed resolution

See the research in #1810386-79: Create workflow to setup multilingual for entity types, bundles and fields β†’ point 7, and 31- .. the end of the comment.
It would be cool to implement some ui improvement to add a hint to what settings have changed, and that the changes will not be saved until the button at the bottom of the screen is clicked.

Suggestion: use the changed css class on the rows that have changed.
Suggestion: add an astrix to changed rows so that change in color of row is not the only clue to changed things.
suggestion: Add a message at the top of the table that things have changed and will not be saved until button at bottom is clicked.

Remaining tasks

  • implement on proposed resolution
  • get feedback from manual testing in browser
  • get feedback from accessibility point of view / using a screen reader

User interface changes

Yes, see above this is a ui issue.

API changes

No api changes anticipated.

πŸ“Œ Task
Status

Needs work

Version

11.0 πŸ”₯

Component
Content translationΒ  β†’

Last updated 2 days ago

No maintainer
Created by

πŸ‡ΊπŸ‡ΈUnited States YesCT

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

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

  • Needs manual testing

    The change/bugfix cannot be fully demonstrated by automated testing, and thus requires manual testing in a variety of environments.

  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

Sign in to follow issues

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.69.0 2024