New issue
Advanced search Search tips

Issue 750465 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
pnangunoori@chromium.org
js...@chromium.org
gsat...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Intl.DateTimeFormat().format returns wrong month names for some historical dates

Reported by wojtek....@gmail.com, Jul 29 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16251

Steps to reproduce the problem:
1. Set your timezone to Warsaw time (UTC +2:00)
2. Run the code from the attached file in browser console
3. Observe results

What is the expected behavior?
All month names shall be correct for all dates.

What went wrong?
In years 1900-1915:
Months April-October are shifted by -1 (April becomes March, May becomes April etc.)

In year 1916:
April is shifted by -1

In year 1917:
April is shifted by -1
October is shifted by -1

and so on, and so on.

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version: 

Works fine on Microsoft Edge. Mozilla Firefox fails even worse (will report).
Check month names validity 1900-2100.txt
994 bytes View Download

Comment 1 by dtapu...@chromium.org, Jul 31 2017

Components: -Blink Blink>JavaScript>Internationalization

Comment 2 by ranjitkan@chromium.org, Aug 2 2017

Labels: Needs-Milestone

Comment 3 by pnangunoori@chromium.org, Aug 3 2017

Cc: pnangunoori@chromium.org
Labels: Needs-Feedback
@wojtek.maj -- Thanks for reporting the issue.

Tested on Chrome Stable #60.0.3112.90, Canary #62.0.3174.2 on Windows 10 and found the below observations:
1. ‘Warsaw’ comes under the timezone “UTC +01:0”.
2. Upon running the code, few months are shifting by -1 (There are also few months which are not specified by you in expected results).

Could you please confirm whether the above mentioned behaviors is what you expected or not. So that we investigate the issue further

Screenshot pertaining to above observations is attached.

Thanks in advance.
750465.png
186 KB View Download

Comment 4 by wojciech...@motorolasolutions.com, Aug 3 2017 

Hey @pnangunoori, yes, that is exactly what I see upon running the test code. 

I believe that this problem is due to Daylight Saving time, Warsaw is UTC+1 or +2 depending on the time of the year.

Comment 5 by hablich@chromium.org, Aug 3 2017

Status: Available (was: Unconfirmed)
Project Member

Comment 6 by sheriffbot@chromium.org, Aug 3

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment