New issue
Advanced search Search tips

Issue 913966 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 913298
Owner: ----
Closed: Dec 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

new Date() returning the time without timezone in Windows 7 OS

Reported by karthikv...@gmail.com, Dec 11

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36

Steps to reproduce the problem:
1. Open console by pressing f12 in chrome browser
2. Type new Date() in the console and press enter.

What is the expected behavior?
new Date() displays Mon Dec 10 2018 16:11:23 GMT-0500 (Eastern Standard Time)

What went wrong?
new Date() displays Mon Dec 10 2018 12:27:23 GMT-0500 (GMT-05:00)

Also in Windows 10 it dispalys perfectly fine.

Since this zone information is used by different APIs, requesting the devs to kindly take a look into this.

Did this work before? Yes 70.0.3538

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

Reading the release notes of the latest version has a point related to a modification for the relative times.

Displaying relative times is now part of the Intl API

I suspect the above change is breaking the time zone information in Windows 7.
 
Labels: Needs-Bisect Needs-Triage-M71
I've encountered a similar problem using Chrome 71 (stable). My OS is set to Berlin timezone, which is currently GMT+1.

The following snippet returns a different result on Windows 7:

new Date(1554069600000).getTimezoneOffset() 

Mac/Linux: -120
Windows 7: -60
Firefox: -120
Safari: -120


It's a rather severe issue for our application since a lot of dates get wrongly formatted on Windows 7 clients.
I've a similar issue.
Chrome 71 running on Windows 7 returns wrong time when timezone is set to Brasilia UTC-3:00 with DST turned on.
I administer a community using the "Invision" platform. When creating an event beyond the transition from "Standard" time to DST (March 10, 2019), Chrome 71 (stable) on Windows 7 displays the incorrect time of the event.

Firefox on Windows 7 displays the correct time. Chrome, Firefox, and Edge on Windows 10 display the correct time. Safari on iOS displays the correct time.

Prior to Chrome 71, I do not recall this being an issue - and as with prior comments, it seems to be an issue only on Windows 7.
Cc: swarnasree.mukkala@chromium.org js...@chromium.org
Labels: -Needs-Bisect Triaged-ET
Mergedinto: 913298
Status: Duplicate (was: Unconfirmed)
Thanks for filing the issue...

The issue seems to be similar to issue id: 913298, hence marking it as a duplicate and tentatively CC'ing jshin@chromium.org.
Note: Please feel free to undupe the issue if it is not the case.

Sign in to add a comment