-
Notifications
You must be signed in to change notification settings - Fork 2.5k
bug(i18n): Header Text does not change after grid is rendered. #4085
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'have the same problem. Is there any workaround today ? Render again with $rootScope.on('$uiI18n') ? |
I have noticed that this issue is even reproducible in the tutorial for i18n. We would welcome a PR for it. |
I have a dropdown of languages.On selecting one language, I want to change the language of Ui-grid menu,pagination,etc.But it is not happening. Presently in my project,I included ui-grid in ng-if and setting ui-i18n="rootScope.langKey",and removed ui-i18n="en" from template in ui-grid.js file.Now ui-grid is rendering in different languages. Please tell me is there any other solution to change language of ui-grid dynamically without modifyng ui-grid.js file. |
…returned value get displayed). Default Menu Items titles now are functions that return translated value, so translation changes at runtime.
…alue get displayed). Default Menu Items titles now are functions that return translated value, so translation changes at runtime.
…returned value get displayed). Default Menu Items titles now are functions that return translated value, so translation changes at runtime.
I am using ui-grid in my project. I am implementing i18n. I have found that header text does not change once the grid rendered. I am using several local languages like English, German, Spanish. When I change from English to German or any other language, the header doesn't. I have to refresh the page to make it working. Is there any workaround for this? I have found you guys have a TODO note for it. Please let me know if there's any workaround for that.
The text was updated successfully, but these errors were encountered: