Apart from 2002 this issue is applicable to other years too.

Able to reproduce this issue on reported version 65.0.3325.181 using Windows 10, Ubuntu 14.04 and Mac 10.13.3. 

This issue is seen from M-60. Hence considering this issue as Non-Regression and marking as Untriaged. 

Can you please confirm the ETA to fix this issue?

re comment 4:

I can't reproduce it on Mac/Linux. 

Google Chrome	65.0.3325.181 (Official Build) (64-bit)
Revision	dc3469be277cc962ba01d9c0cb5bb1a265676c36-refs/branch-heads/3325@{#725}
OS	Mac OS X
JavaScript	V8 6.5.254.41

d=new Date("3/11/2002")
Mon Mar 11 2002 00:00:00 GMT-0800 (PST)
d.getTimezoneOffset()
480

d2=new Date("4/11/2002")
Thu Apr 11 2002 00:00:00 GMT-0700 (PDT)
d2.getTimezoneOffset()
420

---------

Anyway, this should be fixed in Chrome 66 even on Windows if it's only blocked by  bug v8:6031 . If it also requires  bug v8:3547 , you have to wait for Chrome 67. 

v8 6.5.254 branch does not enable 'icu-timezone-data' 
( https://chromium.googlesource.com/v8/v8.git/+/refs/heads/6.5.254/src/flag-definitions.h : icu-timezone-data flag is FALSE by default). 

 nikhilsethi10@gmail.com:

try to launch Chrome with the following command line flag:

--js-flags=--icu-timee-zone-data 

I confirmed that  bug v8:6031  alone is sufficient ( bug v8:3547  is not necessary for this issue). 

So, chrome 66 will work fine (which will have v8 6.6.x). 

wait... even though  bug v8:6031  was fixed in Jan 8,  v8 6.6 branch does not have it:

https://chromium.googlesource.com/v8/v8.git/+/6.6.262/src/flag-definitions.h  (look for 'icu' ; 'icu_timezone_data' flag is still false). 

It's true in v8 6.7.x ;
https://chromium.googlesource.com/v8/v8.git/+/6.7.262/src/flag-definitions.h

If we want to fix it in 66 or 65 branch, it's a 1-line fix ('false' => 'true'). 

jkummerow@:  I thought that branch date for v8 (a.b branch) is similar to the branch date for Chromium "ab" branch (i.e. v8 branch date for 6.6 is only a few days before Chrome's 66 branch date).  Apparently, I was completely off on that. 

#9: What you describe is correct. We are about to branch V8 6.7 for Chrome M67. As of today, there is no V8 6.7 branch (6.7 is just the version number currently associated with "master"), just like there is no Chromium 67 branch (67 is just the version number currently associated with "master"/Canary/Dev).

Thank you for the explanation and sorry for the confusion. 

It turned out that I was confused by the Date in git log (timestamp is Jan 8, 2018), but that's when I made a branch. It's not actually landed in v8 trunk until March 7. See

https://chromium-review.googlesource.com/c/v8/v8/+/857333 . 

So, it makes perfect sense that it's NOT included in 66 branch (let alone 65 branch). 


To  nikhilsethi10@gmail.com;  unless we merge this change to 66 branch (v8 6.6 branch), you have to wait until Chrome 67. 

An alternative is to use the following command line flag:

--js-flags="--icu-timezone-data"

Given that this has been broken on Windows for a long time, it'd be hard to make a case for 65/66 merge even though a fix is a simple flag change. 

It's fixed in 67-to-be. Marking as fixed. 

 Issue 835652  has been merged into this issue.