Skip to content

Add time format preference with system, 12, and 24 options - #7616

Open
larouxn wants to merge 1 commit into
signalapp:mainfrom
larouxn:24_hour_mode_support
Open

Add time format preference with system, 12, and 24 options#7616
larouxn wants to merge 1 commit into
signalapp:mainfrom
larouxn:24_hour_mode_support

Conversation

@larouxn

@larouxn larouxn commented Nov 25, 2025

Copy link
Copy Markdown

First time contributor checklist:

Contributor checklist:

  • My contribution is not related to translations.
  • My commits are in nice logical chunks with good commit messages
  • My changes are rebased on the latest main branch
  • A pnpm run ready passes successfully (more about tests here)
  • My changes are ready to be shipped to users - Cannot say yes until I've seen the preference in a local build.

Description

This pull request aims to add a Time format preference with system, 12, and 24 options so that users can either leave it up to their locale to specify the time format (system) or manually select either 12 or 24 themselves. The preference should appears directly below Language and above Theme.

Screenshot From 2025-11-24 18-13-37

As for the implementation, the one thing that is currently bothering me a bit is the existence of both HourCyclePreference and HourCycleSetting. Unfortunately as the former is already in use for the original 24 hour macOS support implementation, shown below, we cannot settle on just one without refactoring the existing code. 🤔

export enum HourCyclePreference {
Prefer24 = 'Prefer24', // either h23 or h24
Prefer12 = 'Prefer12', // either h11 or h12
UnknownPreference = 'UnknownPreference',
}

Sort of a follow up to 1143c0e, which added 24 hour time format for macOS.

Resolves #4079 (exactly)
Resolves #4252 (sort of, not exactly)

Testing

I added test coverage for this new preference. Additionally I tried running the app locally on my Fedora Workstation 43 (GNOME 49) system but unfortunately I'm seeing some GTK error with the local build. Not sure if that's due to an issue on my end or not.

Screencast.From.2025-11-24.18-14-59.mp4

@larouxn
larouxn force-pushed the 24_hour_mode_support branch from 3c27657 to 9d476bc Compare November 25, 2025 13:17
@larouxn
larouxn force-pushed the 24_hour_mode_support branch from 9d476bc to afae456 Compare December 5, 2025 03:10
@larouxn
larouxn force-pushed the 24_hour_mode_support branch 2 times, most recently from d4a85f4 to c9388b4 Compare December 18, 2025 21:44
@larouxn
larouxn force-pushed the 24_hour_mode_support branch from c9388b4 to 967b1ef Compare January 8, 2026 02:05
@larouxn
larouxn force-pushed the 24_hour_mode_support branch from 967b1ef to e757586 Compare January 21, 2026 22:59
@larouxn

larouxn commented Jan 21, 2026

Copy link
Copy Markdown
Author

Have just rebased this on main. Run of pnpm run ready is clean, no errors. Unfortunately I cannot yet seem to test the setting even at the preferences panel level as I get an error upon trying to open preferences when running that app locally, even on main branch. Maybe someone with a working local dev env can take a minute to test this? 🙏

image

@larouxn
larouxn force-pushed the 24_hour_mode_support branch from e757586 to 7bb9f9d Compare February 4, 2026 21:59
@larouxn
larouxn force-pushed the 24_hour_mode_support branch from 7bb9f9d to 9e48465 Compare February 12, 2026 18:21
@larouxn
larouxn force-pushed the 24_hour_mode_support branch from 9e48465 to f7d0d3d Compare March 3, 2026 20:14
@Gunni

Gunni commented Mar 13, 2026

Copy link
Copy Markdown

Please approve? I need this!

@larouxn
larouxn force-pushed the 24_hour_mode_support branch from f7d0d3d to 24f8676 Compare March 13, 2026 14:31
@larouxn

larouxn commented Mar 13, 2026

Copy link
Copy Markdown
Author

Thanks for the support! Unfortunately I'm still unable to test the change with the locally running app. Can boot the app but cannot access Preferences let alone actual messages. See below, error after I clicked Preferences.

image

We definitely need someone who can run it to test and make sure that these changes actually do what they say they do (i.e. 12-hour, 24-hour, system setting) beyond what the tests demonstrate.

@larouxn
larouxn force-pushed the 24_hour_mode_support branch 2 times, most recently from f5ddc3b to 66402ee Compare April 8, 2026 22:36
@larouxn
larouxn force-pushed the 24_hour_mode_support branch from 66402ee to d0de182 Compare April 27, 2026 21:20
@larouxn
larouxn force-pushed the 24_hour_mode_support branch from d0de182 to dd4450a Compare June 10, 2026 18:45
@larouxn
larouxn force-pushed the 24_hour_mode_support branch from dd4450a to c48dc68 Compare July 4, 2026 15:34
@larouxn
larouxn force-pushed the 24_hour_mode_support branch from c48dc68 to 051c8fc Compare July 9, 2026 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Timestamp format should match system time format Add option for 24-hour clock

2 participants