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.

Comments

mgifford’s picture

Just adding related links about the Language of Parts:

http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-other-lang-id.html
http://groups.drupal.org/node/145894
http://drupal.org/project/issues/search/drupal?issue_tags=language%20of%...

Having a message pop up like it does for the table sort would seem to be needed.

mgifford’s picture

Issue tags: +language of parts

tagging

YesCT’s picture

Assigned: YesCT » Unassigned

unassigning

Gábor Hojtsy’s picture

Component: translation_entity.module » content_translation.module
mgifford’s picture

Issue summary: View changes

Bump to 8.1?

yoroy’s picture

Version: 8.0.x-dev » 8.2.x-dev
Issue tags: +Needs design

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.

yoroy’s picture

Issue tags: +Needs screenshots, +sprint

A screenshot to clarify the problem would help to mock up possible solutions.

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.