[MGNLUI-3913] i18n: Checkboxes should stay checked across languages Created: 15/Jun/16  Updated: 13/Mar/17  Resolved: 08/Mar/17

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.4.6, 5.4.7
Fix Version/s: 5.4.12, 5.5.3

Type: Bug Priority: Neutral
Reporter: Karsten Martin Assignee: Ngoc Nguyenthanh
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: 0.5h

Attachments: PNG File 14.06.2016_magnolia_roche_i8n_locations_checkbox_value_cross_languages_CURRENT.png     PNG File 14.06.2016_magnolia_roche_i8n_locations_checkbox_value_cross_languages_EXPECTED.png    
Issue Links:
Cloners
Relates
relates to MGNLUI-3955 Switching authoring locale changes va... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Visible to:
Ciaran Burkett, Frank Sommer, Gernot Fussan, Joerg von Frantzius, Sebastian Bauch, Sergej Steinbach, Steven Roth, Tim Arnhold
Sprint: Saigon 86
Story Points: 1

 Description   

CURRENT:
Checkboxes during setup for an item inside an app like locations, will not share its value across languages when the connected value itself is setup for i18n but the checkbox itself is not,

Reproduction:

  1. enter magnolia admin central
  2. enter the Tours app
  3. create/edit some tour
  4. setup the item, mark the checkbox (Feature this item) in LANGUAGE 1
  5. switch to LANGUAGE 2
    Result: The value of the checkbox beeing NOT i18n sensible is loosing its value, so it is still reacting to the language change eventhough it should not.

EXPECTED:
When checkboxes in apps are setup not to be i18n sensible they should keep their value during language change.


CURRENT EXPECTED


 Comments   
Comment by Mikaël Geljić [ 05/Mar/17 ]

To verify that MGNLUI-3955 solves this, when integrated (cc ngoc.nguyenthanh).

Comment by Hieu Nguyen Duc [ 08/Mar/17 ]

This issue's been fixed by MGNLUI-3955.

Generated at Mon Feb 12 09:11:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.