Closed Bug 1884075 Opened 2 years ago Closed 2 years ago

Asia/Almaty Intl

Categories

(Core :: JavaScript: Internationalization API, enhancement)

Firefox 123
enhancement

Tracking

()

RESOLVED DUPLICATE of bug 1879488

People

(Reporter: iamceltic9, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0

Steps to reproduce:

try this lines of code
let date = new Date('2024-10-10 00:00:00Z')
console.log(new Intl.DateTimeFormat('ru-RU', { hour: 'numeric', minute: 'numeric', timeZone: 'Asia/Almaty' }).format(date))

Actual results:

the 'Asia/Almaty' is currently in UTC+05:00 timezone, but Intl converts it to +06:00 timezone, so I get time 06:00 instead of 05:00

Expected results:

time transforming should work like this:
if date is BEFORE 1st of March 00:00:00, then 'Asia/Almaty' timezone should be UTC+06:00
if date is AFTER 1st of March 00:00:00, then 'Asia/Almaty' timezone should be UTC+05:00

The Bugbug bot thinks this bug should belong to the 'Core::Internationalization' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Internationalization
Product: Firefox → Core

Bug 1879488 updates to tzdata 2024a, which includes the time zone update for Kazakhstan. So when Firefox 124 gets released in about two weeks, the time zone information for "Asia/Almaty" will be correct again.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Component: Internationalization → JavaScript: Internationalization API
Duplicate of bug: 1879488
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.