You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1: VISTA IE9
2: Steps to reproduce
Cold load application http://mf-geoadmin3.bgdi.admin.ch/main/prod/
3: Result
non translated technical names appear on load in container
4: Expected Result
Application does show correct language on load.
Otherwise user thinks application is slow. This can especially observed on older mobile and slow connections... I know it is picky, but it is the first thing the user sees fomr the new app ... I think jeiziner observed the same thing
5: if possible: workaround
WAIT!
6: link to file : attache it to github
The text was updated successfully, but these errors were encountered:
This is not a bug, this is a feature -> see the FOUC paragraph here: http://pascalprecht.github.io/angular-translate/#/guide/10_asynchronous-loading
Nevertheless, I also find that not so nice. We could try the proposed workaround. I was also think to show the app only when it's translated (with a loading app message) -> To be discussed.
I think that we should be able to add the lang files into some Angular $http cache at build time, as we already do for the directives' HTML partials. This may require a (probably simple and small) patch to angular-translate though.
Search Engine Optimization is something we want to discuss as well. I'd like to understand if client-side translation is compatible with multi-language indexing by search engines.
1: VISTA IE9
2: Steps to reproduce
Cold load application http://mf-geoadmin3.bgdi.admin.ch/main/prod/
3: Result
non translated technical names appear on load in container
4: Expected Result
Application does show correct language on load.
Otherwise user thinks application is slow. This can especially observed on older mobile and slow connections... I know it is picky, but it is the first thing the user sees fomr the new app ... I think jeiziner observed the same thing
5: if possible: workaround
WAIT!
6: link to file : attache it to github
The text was updated successfully, but these errors were encountered: