It's the intended behavior. The problem with honoring the locale on the user preference is that the user is not available if not logged-in, so we need to rely on the cookie if the user is not available. This further complicates things as if the user uses the dropdown prior to authenticating the cookie is updated, but not the user. If we then switched to whatever the user had set when the user was authenticated we'd revert the changes the user just did.

Then why would different users use the same browser aka share a locale cookie? I don't think that's a frequent thing, especially not as os has user support, browsers have support for profiles and then there's also incognito sessions. Finally, even if users do share a machine would they not then in most case have the same locale?

On 2 June 2016 at 15:21, Thomas Raehalme <thomas.raehalme@aitiofinland.com> wrote:
Hi,

While localizing the Keycloak UI for end-users (login, account, email) we noticed that the user's locale changes to whatever locale is active when logging in. Is this intended behavior?

If it is, I think it would be better to honor the locale on user preferences, and allow the user to change the locale in the account settings instead. The locale setting on the browser may not reflect the desired locale set on user preferences. 

What do you think?

Best regards,
Thomas

_______________________________________________
keycloak-dev mailing list
keycloak-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev