Contrib.social

Language of (optgroup) array keys and interface language at render time should be same

Open on Drupal.org →
Created on 12 September 2015, about 9 years ago
Updated 23 May 2023, over 1 year ago

Problem/Motivation

When form builds optgroup elements they sometimes uses entities' properties as a group name at the form build time, later this forms could be build in different language interface context so option names could be in different language

Proposed resolution

Check the code flow and try use string-wrapper as long as possible for group names

Remaining tasks

have a test that insures that having right interface language when working with option-group element in build and render times

User interface changes

no

API changes

no

Data model changes

no

🐛 Bug report
Status

Closed: cannot reproduce

Version

9.5

Component
Other  →

Last updated about 7 hours ago

Created by

🇫🇷France andypost

Live updates comments and jobs are added and updated live.
  • 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.

  • Comment over 1 year ago →
    🇺🇸United States Kristen Pol Santa Cruz, CA, USA

    As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" almost a year ago.

    Since there has been no additional information provided since the issue was postponed last year, I'm marking the issue "Closed (cannot reproduce)". If anyone can provide complete steps to reproduce the issue (starting from "Install Drupal core"), document those steps in the issue summary and set the issue status back to "Active" [or "Needs Work" if it has a patch, etc.].

    Thanks!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024