New issue
Advanced search Search tips

Issue 852298 link

Starred by 7 users
Status: Duplicate
Merged: issue 849404
Owner:
js...@chromium.org
Closed: Jun 2018
Cc:
vamshi.kommuri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

New Date(<number>) constructs wrong time, if number is below a specific value

Reported by haefe...@googlemail.com, Jun 13 2018 
UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Steps to reproduce the problem:
1. Open console
2. new Date(-2447483648000)

What is the expected behavior?
a Date with GMT+0200 (if your local timezone is CEST)

What went wrong?
GMT+0053 and TIME is not Displayed CORRECT (~7 min incorrect)

Did this work before? Yes 66

Chrome version: 67.0.3396.87  Channel: stable
OS Version: 6.3
Flash Version:

Comment 1 by tkent@chromium.org, Jun 13 2018

Components: -Blink Blink>JavaScript

Comment 2 by krajshree@chromium.org, Jun 13 2018

Labels: Needs-Bisect Needs-Triage-M67

Comment 3 by vamshi.kommuri@chromium.org, Jun 14 2018

Cc: vamshi.kommuri@chromium.org
Labels: -Pri-2 -Needs-Bisect Triaged-ET OS-Linux OS-Mac Pri-1
Owner: js...@chromium.org
Status: Assigned (was: Unconfirmed)
Thanks for filing the issue!

As this issue looks very similar to that of  Issue 852321 , hence assigning it to jshin@ for further action/confirmation and it's probably WAI.
Note: Got the similar break as in  Issue 852321 
i.e., Good build: 67.0.3389.0
      Bad build : 67.0.3390.0

Comment 4 by goo...@tabtoo.com, Jun 16 2018 

Do you have an ETA for a fix? What is WAI? Thanks.

Comment 5 by js...@chromium.org, Jun 16 2018

Labels: -Needs-Triage-M67
Status: WontFix (was: Assigned)
In 1892, the timezone offset was different from today.

Comment 6 by js...@chromium.org, Jun 20 2018

Mergedinto: 849404
Status: Duplicate (was: WontFix)
►

Sign in to add a comment