Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
A handful of timezone related fixes were added into 0.5.33 release of moment-timezone. An example for a scenario in which current UI2 behaviour is not correct is a user from Australia, where the submission time showed on UI2 is one hour ahead of the actual time.
Unfortunately moment-timezone data range files have been renamed, which is a breaking change from the point of view of emberjs. Including all timezones will increase the overall size of UI2 by an additional ~6 kbs.