electron: Electron 32/33 `Intl` API returns `Etc/Unknown` time zone
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a bug report that matches the one I want to file, without success.
Electron Version
32.2.3
What operating system(s) are you using?
Windows
Operating System Version
Windows 11 Home Single Language (Build 22631.4391)
What arch are you using?
x64
Last Known Working Electron version
30.5.1
Expected Behavior
Intl.DateTimeFormat().resolvedOptions().timeZone should return “Africa/Johannesburg”
Actual Behavior
Intl.DateTimeFormat().resolvedOptions().timeZone returns “Etc/Unknown”
Testcase Gist URL
No response
Additional Information
It just happens on Windows 11 Home Single Language (Build 22631.4391). On Window 11 Home/Pro works fine.
It is working fine on Electron 30.x, as soon as I update to 32 or 33 its breaks. There must be a regression.
You can test by opening dev tools and typing Intl.DateTimeFormat().resolvedOptions().timeZone.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 18 (4 by maintainers)
The Chromium version is likely a misdirection - Chrome uses V8 to determine your timezone, which in turn relies on Unicode ICU (https://v8.dev/docs/i18n).
I haven’t checked this myself but here’s my theory:
Just a guess but a pretty confident one
Any news? @felixrieseberg @codebytere @dsanders11 @VerteDinde @deepak1556
Can you please check this? It’s quite critical, it affects bunch of users and it is reproducible. Can you check if ICU version is updated?
It’s set to South Africa locale, English language.
Works fine on latest Chrome browser (Chromium 130.0.6723.117 Stable). Does not work neither on Electron 33.2.0 (Chromium 130.0.6723.118) nor Electron 32.2.3 (Chromium 128.0.6613.186).