So setting timezone in ClientDetails by LoginViewSupport is currently useless.
The browser timezone should be used if the user timezone is not set. Consider also introducing the autoTimeZone attribute in the User entity to control whether the browser timezone should be used (or a special value in the timezones list to not change the model).
Currently for the standard scaffolded
User
entity that implementsHasTimeZone
the browser timezone is ignored even when the user timezone is not set. See https://github.com/jmix-framework/jmix/blob/49e8076cdcd2925a39bf0c0c23848c666705f4b5/jmix-core/core/src/main/java/io/jmix/core/security/impl/CurrentAuthenticationImpl.java#L118-L125So setting timezone in
ClientDetails
byLoginViewSupport
is currently useless.The browser timezone should be used if the user timezone is not set. Consider also introducing the
autoTimeZone
attribute in the User entity to control whether the browser timezone should be used (or a special value in the timezones list to not change the model).