[MGNLUI-4654] Validation on language switch in Content App with fallback language may trap user Created: 24/Sep/18 Updated: 24/Sep/18 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | dialogs, forms |
| Affects Version/s: | 5.5.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Dominik Briner | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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
|
| Description |
|
We have a content app for an EE-customer in which content is filled out for multiple languages. However, only the fallback language is required as some content should only be available in that language. If you enter no content for a language and then try to access the content in that language, the content of the fallback language is automatically substituted. Due to the changes in Due to this, one miss click can mean that the user loses all the content he entered. In |