New issue
Advanced search Search tips

Issue 853463 link

Starred by 1 user
Status: Duplicate
Merged: issue 849404
Owner: ----
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Issue in getting TimezoneOffset from a Date object

Reported by madurai....@gmail.com, Jun 16 2018 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Steps to reproduce the problem:
1. In 67.0.3396.79
2. Open the developer console
3. new Date(1900, 0, 1).getTimezoneOffset() 
4. it return 321

What is the expected behavior?
1. Till 66.0.3359.181 version it works correctly
2. new Date(1900, 0, 1).getTimezoneOffset()
3. it return 330

What went wrong?
I am from IST timezone, it returns 321 instead of 330 for the years before 1970.

Did this work before? Yes It worked till 66.0.3359.181

Chrome version: 66.0.3359.181  Channel: n/a
OS Version: OS X 10.13.4
Flash Version:

Comment 1 by susan.boorgula@chromium.org, Jun 17 2018

Labels: Needs-Milestone Needs-Bisect

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

Labels: -Needs-Bisect Triaged-ET
Mergedinto: 852321
Status: Duplicate (was: Unconfirmed)
The issue looks similar to issue id: 852321. Hence, merging into issue id: 852321.
Please feel free to undupe the same if not the case.

Thanks...!!

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

Mergedinto: -852321 849404
►

Sign in to add a comment