New issue
Advanced search Search tips

Issue 715261 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Date objects not properly localizing to computer's timezone

Project Member Reported by tgunderson@google.com, Apr 25 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
1. Create new date object. i.e. var d = new Date(2017-04-29T16:00:00.000)
2. Log date object to console. console.log(d)
3. Observe incorrect date object: Sat Apr 29 2017 16:00:00 GMT-0700 (PDT)
3. Repeat with Safari and observe correct date object: Sat Apr 29 2017 09:00:00 GMT-0700 (PDT)

What is the expected behavior?
Prior to this version of Chrome I would get the correctly localized time from a date object originally in UTC format.

What went wrong?
The time is no longer localizing returning the time in UTC instead of PDT in my case.

Did this work before? Yes 57.0.2987.133

Chrome version: 58.0.3029.81  Channel: stable
OS Version: OS X 10.12.4
Flash Version: 

Please fix ASAP!
 
Mergedinto: 714301
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment