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
Signal on Mac OS X does not respect the operating system settings for date/time formatting.
Steps to Reproduce
1 Go to System Preferences
2 Select Language & Region
3 Select Switzerland
3 Select Time Format: 24 hours time format
4 Launch Signal
5 Look at messages that are in the past.
Actual Result:
Signal displays times in US format, i.e. Tue 5.56 pm.
Expected Result:
Signal displays times in the chat conversation 24 hours format, i.e. Tue 17:56 like for instance the iOS version.
Screenshots
System Settings:
Conversation Mac OS X:
Conversation iOS:
Platform Info
Signal Version: v5.12.2
Operating System: Mac OS X 11.5.1 (20G80)
Linked Device Version: iOS 14.7.1
Link to Debug Log
There are no logs, as the bug only appears for messages in the past.
Note that bug #5248 describes a similar issue for Windows.
The text was updated successfully, but these errors were encountered:
scottnonnenberg-signal
changed the title
Signal does not respect regional settings for date/time on Mac OS X
Respect regional settings for date/time (beyond the default locale settings)
Aug 20, 2021
Bug Description
Signal on Mac OS X does not respect the operating system settings for date/time formatting.
Steps to Reproduce
1 Go to System Preferences
2 Select Language & Region
3 Select Switzerland
3 Select Time Format: 24 hours time format
4 Launch Signal
5 Look at messages that are in the past.
Actual Result:
Signal displays times in US format, i.e. Tue 5.56 pm.
Expected Result:
Signal displays times in the chat conversation 24 hours format, i.e. Tue 17:56 like for instance the iOS version.
Screenshots
System Settings:
Conversation Mac OS X:
Conversation iOS:
Platform Info
Signal Version: v5.12.2
Operating System: Mac OS X 11.5.1 (20G80)
Linked Device Version: iOS 14.7.1
Link to Debug Log
There are no logs, as the bug only appears for messages in the past.
Note that bug #5248 describes a similar issue for Windows.
The text was updated successfully, but these errors were encountered: