[MAGNOLIA-1619] when validation fails for required fields, localization of those fields is broken. Created: 05/Jul/07 Updated: 23/Jan/13 Resolved: 05/Jul/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.0 Beta 1 |
| Fix Version/s: | 3.0 Final |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Miner | Assignee: | Chris Miner |
| Resolution: | Fixed | 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 |
|
1. setup a dialog with i18nBasename found: rather than my localized string being displayed in the alert panel, the key for the string is displayed. This is due to the fact that during validation a dialog impl doesn't have a parent. Setting the parent before validation seems to fix this problem. |
| Comments |
| Comment by Chris Miner [ 05/Jul/07 ] |
|
updated 3.0 and trunk fields now localized. |