New issue
Advanced search Search tips

Issue 821842 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 819686
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Different Timezone depending on Date Constructor

Reported by rodrigo....@gmail.com, Mar 14 2018

Issue description

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

Steps to reproduce the problem:
1. Run `new Date()` // I got GMT-0300 (Hora oficial do Brasil)
2. Run `new Date(0)` // I got GMT-0200 (Horário brasileiro de verão) - daylight savings

What is the expected behavior?
1. Run `new Date()` // GMT-0200 (Horário brasileiro de verão) - daylight savings
2. Run `new Date(0)` // GMT-0200 (Horário brasileiro de verão) - daylight savings

What went wrong?
I suppose the daylight should be considered in the two cases... 

Thank you.

Did this work before? N/A 

Chrome version: 64.0.3282.186  Channel: stable
OS Version: 10.0
Flash Version:
 
bug_chrome_daylight_timezone.png
3.5 KB View Download
Maybe same problem in  Issue #819686 
Labels: Needs-Triage-M64
Components: -Blink Blink>JavaScript>Internationalization

Comment 4 by ajha@chromium.org, Mar 22 2018

Cc: js...@chromium.org
Labels: Triaged-ET
Mergedinto: 819686
Status: Duplicate (was: Unconfirmed)
This issue looks similar to  issue 819686 . Hence merging this issue to  issue 819686 .

Thanks..

Sign in to add a comment