Asia/Kolkata as system time zone on macOS is not recognized by `Intl`
Categories
(Core :: JavaScript: Internationalization API, defect)
Tracking
()
People
(Reporter: abhishek.prince.madhu, Unassigned)
Details
Attachments
(5 files)
Screenshot of the bug.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36
Steps to reproduce:
- Set system Timezone to Asia/Kolkata on MacOS Sonoma - Version 14.0 (23A339)
- Install Thunderbird 115 or above (all of stable, beta and daily) on MacOS Sonoma - Version 14.0 (23A339)
- Go to "Calendar" view
- Check and confirm that the Settings->Timezone setting is set to "Use System Timezone" (calendar.timezone.useSystemTimezone == true, which leaves calendar.timezone.local to "UTC")
The bug can be noticed at this point.
I tried a few other workarounds.
Part 2 - Trying workarounds
4. Now, set the TZ in Thunderbird to Asia/Calcutta (as Asia/Kolkata is new name, Asia/Calcutta is older name of same timezone).
5. Check the time again.
Actual results:
The current time shown by the calendar is 11 hours behind the current time on the system (and 5:30 hours behind UTC, which is the automatically detected TZ).
My system's TZ is UTC+5:30 (Asia/Kolkata).
Additional details of expected vs actual results, especially screenshots, are available here (https://support.mozilla.org/en-US/questions/1424864) as Bugzilla is allowing only one screenshot.
After changing the TZ to Asia/Calcutta, The current time shown by the calendar is now 5:30 hours behind the current time at Asia/Calcutta. Since Asia/Calcutta is UTC+5:30, it now shows UTC time, even though timezone is set to Asia/Calcutta.
Expected results:
- The current time shown by the calendar should be the same as the current system timezone when using System Timezone.
- The current time shown by the calendar should be the same as the time at the timezone when using specific timezone.
|
||
Updated•2 years ago
|
|
||
Comment 1•2 years ago
|
||
Could you open the JavaScript console (either via the menu, Tools > Developer Tools > Developer Toolbox, or keyboard shortcut, which is probably Cmd+Shift+I) and enter Intl.DateTimeFormat().resolvedOptions().timeZone and provide the result here? Additionally, cal.timezoneService.getTimezone("Asia/Kolkata").icalComponent.toString()'s output would be helpful.
|
Reporter | |
Comment 2•2 years ago
|
||
|
|
Reporter | |
Comment 3•2 years ago
|
||
|
|
Reporter | |
Comment 4•2 years ago
|
||
Hi Sean,
I apologize for the delay - the time you commented was 4AM for me.
Please find the requested details below. I couldn't find a way to attach a screenshot, and the paste-attachment didn't work, so I am pasting the output here.
(I am more than willing to be available during your time and show you the issue/run additional commands/steps in case you think it will help. Just let me know a day in advance).
Also, note that currently the TimeZone in the Calendar Settings is set to Manual->Asia/Calcutta.
calendar.timezone.local = "Asia/Calcutta"
calendar.timezone.useSystemTimezone = false
I don't know why TZ is resolved to "UTC".
>>> Intl.DateTimeFormat().resolvedOptions().timeZone
"UTC"
>>> cal.timezoneService.getTimezone("Asia/Kolkata").icalComponent.toString()
"BEGIN:VTIMEZONE
TZID:Asia/Kolkata
X-TZINFO:Asia/Kolkata[2023c]
BEGIN:STANDARD
TZOFFSETTO:+055320
TZOFFSETFROM:+055328
TZNAME:Asia/Kolkata(STD)
DTSTART:18540628T000000
RDATE:18540628T000000
END:STANDARD
BEGIN:STANDARD
TZOFFSETTO:+052110
TZOFFSETFROM:+055320
TZNAME:Asia/Kolkata(STD)
DTSTART:18700101T000000
RDATE:18700101T000000
END:STANDARD
BEGIN:STANDARD
TZOFFSETTO:+053000
TZOFFSETFROM:+052110
TZNAME:Asia/Kolkata(STD)
DTSTART:19060101T000000
RDATE:19060101T000000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETTO:+063000
TZOFFSETFROM:+053000
TZNAME:Asia/Kolkata(DST)
DTSTART:19411001T000000
RDATE:19411001T000000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETTO:+053000
TZOFFSETFROM:+063000
TZNAME:Asia/Kolkata(STD)
DTSTART:19420515T000000
RDATE:19420515T000000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETTO:+063000
TZOFFSETFROM:+053000
TZNAME:Asia/Kolkata(DST)
DTSTART:19420901T000000
RDATE:19420901T000000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETTO:+053000
TZOFFSETFROM:+063000
TZNAME:Asia/Kolkata(STD)
DTSTART:19451015T000000
RDATE:19451015T000000
END:STANDARD
END:VTIMEZONE"
|
|
Reporter | |
Comment 5•2 years ago
|
||
|
|
||
Comment 6•2 years ago
|
||
Thank you for providing the requested information. Unfortunately, as to the naming of "Asia/Calcutta", this is data that we draw from an external project, the version of which is controlled by the Firefox team. I'm working to find better information on when we will update to a version which prefers "Asia/Kolkata" and will update when I have it.
As to the failure to recognize your system time zone, it appears this issue is likely also either in Firefox or ICU, the external library we depend on. I'll look into this as well and follow up with further information.
|
|
||
Updated•2 years ago
|
|
||
Comment 7•2 years ago
|
||
Does Thunderbird contain the fix for bug 1848615?
|
|
||
Comment 8•2 years ago
|
||
(In reply to André Bargull [:anba] from comment #7)
Does Thunderbird contain the fix for bug 1848615?
We should have this fix as of 115.3.0. Abhishek, could you verify your Thunderbird version and, if it's older than 115.3.0, update to the latest and test if this bug is still present?
|
|
Reporter | |
Comment 9•2 years ago
|
||
|
|
Reporter | |
Comment 10•2 years ago
|
||
I see from my notes that the problems existed on beta version 118.0b6 (64-bit) as well as in the daily version 119.0a1 (2023-09-23) (64-bit) for MacOS. Do you want me to download the latest daily version and check again?
|
|
||
Comment 11•2 years ago
|
||
(In reply to Abhishek Madhu from comment #10)
Do you want me to download the latest daily version and check again?
No, there's no need to do that. I think this bug is actually the same as bug 1856428, which also affects Firefox on MacOS Sonoma.
|
||
Comment 12•2 years ago
|
||
:anba, should we just mark this as a duplicate of bug 1856428?
|
|
||
Comment 13•2 years ago
|
||
Yes, I think we can close it as a dup of bug 1856428.
Description
•