-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
3.4.6
-
None
-
None
Timebox: 3SP – research the problem, make proper estimate for the fix.
Steps to reproduce
- Use blossom sample project to quickly reproduce the issue.
- There must be at least two configured languages for authoring.
- Add the following switchable field to any of the existing components (eg. text)
cfg.fields.switchable("testme").options( new RealOptionBuilder().value("test1_text1").label("test1").selected(), new RealOptionBuilder().value("test2_text2").label("test2") ).fields( cfg.fields.text("test1_text1").label("Text 1").required().i18n(), cfg.fields.text("test2_text2").label("Text 2").required().i18n() ).required().i18n()
- Add that component to any page
- When dialog opens, leave default language empty and switch to another language
- Fill all the required values and save.
Expected results
Dialog closes and information is stored
Actual results
Nothing happens due to validation on the switchable field occurring in the first language tab (Same than in MGNLUI-6830)
Workaround
Don't use selected() so the switchable field is not expanded in the first language tab. This wouldn't be desirable when fields of switchable are required as you could save without filling them.
Development notes
This is not happening when using switchable field out of blossom scope. It has been reproduced also with 3.4.7-SNAPSHOT
Acceptance criteria
- is related to
-
MGNLUI-6830 No visual feedback on field validation of default language when dialog/form is showing another language
- Closed