New issue
Advanced search Search tips

Issue 689258 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 687751
Owner: ----
Closed: Feb 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Incorrect DST transition date for certain years in the Asia/Jerusalem time zone

Reported by mj1...@gmail.com, Feb 1 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36

Steps to reproduce the problem:
1. Set time zone to Jerusalem (Israel)
2. In Chrome JS console check the following:

console.log(new Date(2013, 2, 22, 1, 0, 0, 0).toString());
console.log(new Date(2013, 2, 22, 2, 0, 0, 0).toString());
console.log(new Date(2013, 2, 22, 3, 0, 0, 0).toString());
console.log(new Date(2013, 2, 29, 1, 0, 0, 0).toString());
console.log(new Date(2013, 2, 29, 2, 0, 0, 0).toString());
console.log(new Date(2013, 2, 29, 3, 0, 0, 0).toString());

What is the expected behavior?
Should emit:

Fri Mar 22 2013 01:00:00 GMT+0200 (Jerusalem Standard Time)
Fri Mar 22 2013 02:00:00 GMT+0200 (Jerusalem Standard Time)
Fri Mar 22 2013 03:00:00 GMT+0200 (Jerusalem Standard Time)
Fri Mar 29 2013 01:00:00 GMT+0200 (Jerusalem Standard Time)
Fri Mar 29 2013 03:00:00 GMT+0300 (Jerusalem Daylight Time)
Fri Mar 29 2013 03:00:00 GMT+0300 (Jerusalem Daylight Time)

What went wrong?
Actual results:

Fri Mar 22 2013 01:00:00 GMT+0200 (Jerusalem Standard Time)
Fri Mar 22 2013 03:00:00 GMT+0300 (Jerusalem Daylight Time)
Fri Mar 22 2013 03:00:00 GMT+0300 (Jerusalem Daylight Time)
Fri Mar 29 2013 01:00:00 GMT+0300 (Jerusalem Daylight Time)
Fri Mar 29 2013 02:00:00 GMT+0300 (Jerusalem Daylight Time)
Fri Mar 29 2013 03:00:00 GMT+0300 (Jerusalem Daylight Time)

Did this work before? N/A 

Chrome version: 56.0.2924.76  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

Jerusalem springs-forward on the Friday before the Last Sunday in March.   Chrome gets the date a week wrong for 2012, 2013, 2019 but not for other years.

The IANA TZ Database has the correct data, and so does the Windows registry, but somehow it is not coming through correctly.

 

Comment 1 by ajha@chromium.org, Feb 7 2017

Labels: Needs-Bisect Needs-Triage-M56
Labels: -Needs-Bisect -Needs-Triage-M56
Mergedinto: 687751
Status: Duplicate (was: Unconfirmed)
This issue looks similar to the issue id: 687751. Hence, merging into the issue id: 687751.

Thanks...!!

Sign in to add a comment