New issue
Advanced search Search tips

Issue 860254 link

Starred by 2 users
Status: Duplicate
Merged: issue 849404
Owner:
js...@chromium.org
Closed: Jul 17
Cc:
js...@chromium.org
viswa.karala@chromium.org
gsat...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Date problem with some values: In 1963, Rome

Reported by alessand...@gmail.com, Jul 4 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
console.log(new Date(-209440800000).getDate())

What is the expected behavior?
Day should be 14

What went wrong?
On chrome 67 day is 13

Did this work before? Yes 

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:

Comment 1 by alessand...@gmail.com, Jul 4 

http://jsfiddle.net/rLjQx/73758/
ff_date.JPG
12.7 KB View Download
ch_date.JPG
11.9 KB View Download

Comment 2 by schenney@chromium.org, Jul 4

Components: -Blink Blink>JavaScript
Labels: -Pri-2 Pri-1
Making it a P1 to get attention. I don't know how serious this is. Re-prioritize as needed.

Comment 3 by krajshree@chromium.org, Jul 5

Labels: Needs-Bisect Needs-Triage-M67

Comment 4 by viswa.karala@chromium.org, Jul 5

Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on chrome reported version# 67.0.3396.99 using Windows-7 & 10 with steps mentioned below:
1) Launched chrome reported version opened Devtools > Console
2) Given "console.log(new Date(-209440800000).getDate())" in console, seen output as "14"
3) Also tried using URl: http://jsfiddle.net/rLjQx/73758/, seen output as "14"

@Reporter: Please find the attached screencast for your reference and provide your feedback on it. Please try to test this issue by creating new person with no apps and extensions in it and let us know if the issue still persists.

Thanks!
860254.mp4
1.2 MB View Download

Comment 5 by alessand...@gmail.com, Jul 5 

Thank you viswa. Maybe it depends on timezone? I'm in italy.
Checking offsets actually chrome give me a different value for 1963's date.

--
Tests on Chrome

TimezoneOffsets

today: -120
in 1963: -60
--
Tests on Firefox

TimezoneOffsets

today: -120
in 1963: -120
--

jsfiddle updated: 
http://jsfiddle.net/rLjQx/74300/
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 5

Cc: viswa.karala@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 7 by tkent@chromium.org, Jul 5

Cc: js...@chromium.org

Comment 8 by swarnasree.mukkala@chromium.org, Jul 6

Components: -Blink>JavaScript Blink>JavaScript>Internationalization
@jshin : We have been seeing mutiple date/time offset isssues on M-67.Could you please look into these.

Adding component team Blink>JavaScript>Internationalization.

Thanks!

Comment 9 by swarnasree.mukkala@chromium.org, Jul 9 

Issue is not re-pro in India timezone ,hence requesting @Jshin for more inputs on this issue.

Thanks !

Comment 10 by swarnasree.mukkala@chromium.org, Jul 11

Owner: js...@chromium.org
Status: Assigned (was: Unconfirmed)
Assigning to @jshin, as we have been seeing multiple date/time offset issues on M-67.

Thanks.!

Comment 11 by susan.boorgula@chromium.org, Jul 11 

 Issue 862084  has been merged into this issue.

Comment 12 by js...@chromium.org, Jul 17

Mergedinto: 849404
Status: Duplicate (was: Assigned)
Summary: Date problem with some values: In 1963, Rome (was: Date problem with some values)
This is WAI. In 1963, Europe/Rome has a different timezone offset than today. 

In 1963, Europe/Rome was UTC-1 year-round (no DST). See 
https://www.timeanddate.com/time/zone/italy/rome . 

Firefox does not teke into account that historical offset.
►

Sign in to add a comment