New issue
Advanced search Search tips

Issue 865022 link

Starred by 1 user
Status: Duplicate
Merged: issue 854201
Owner:
js...@chromium.org
Closed: Jul 23
Cc:
swarnasree.mukkala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Chrome doesn't check option daylight saving time (DST).

Reported by nikitoz...@gmail.com, Jul 18 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. set the timezone in windows to UTC+0 (London) with disabled DST option (or any other timezone with DST option enabled)

2. open Chrome, execute the script in Chrome console:
new Date()

3. see that date comes with DST offset (+1 hour), despite of the disabled DST option 

What is the expected behavior?
new Date()

script should return time considering the DST option

What went wrong?
Chrome doesn't considering the DST option, unlike the others browsers do. 

Did this work before? Yes Version 66.0.3359.139 (Official Build) (64-bit)

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 10.0
Flash Version: 

other browser such as Firefox considering the DST time (don't forget to restart browsers when changing DST option)

Comment 1 by nikitoz...@gmail.com, Jul 18

chromebug.jpg
44.4 KB View Download

Comment 2 by nikitoz...@gmail.com, Jul 18 

please use that script 
document.writeln(new Date())


instead of specified in topic

Comment 3 by viswa.karala@chromium.org, Jul 18

Labels: Needs-Bisect Needs-Triage-M67

Comment 4 by swarnasree.mukkala@chromium.org, Jul 19

Cc: swarnasree.mukkala@chromium.org js...@chromium.org
Labels: Triaged-ET
This issue seems to be similar to issue id 851804. 

@jshin - Could you please confirm whether we can merge this issue with 851804.

Thanks !

Comment 5 by swarnasree.mukkala@chromium.org, Jul 20

Cc: -js...@chromium.org
Labels: -Pri-2 -Needs-Bisect hasbisect-per-revision ReleaseBlock-Stable M-68 M-69 Target-67 FoundIn-67 Target-68 RegressedIn-67 FoundIn-68 FoundIn-69 Target-69 Pri-1
Owner: js...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce issue on reported chrome version 67.0.3396.99 & on latest chrome 69.0.3496.0 using Windows 10. Hence providing bisect information below.

Bisect Info:
================
Good build: 67.0.3395.0
Bad build: 67.0.3396.0

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/36c7581411a133a52e8b73534765aab824a2d1eb..43db8c3666e41c337498ae066f0a2c012f888350

suspect: https://chromium.googlesource.com/v8/v8/+/ae314567068815d494ef206db54a887cdd614db7

Reviewed-on: https://chromium-review.googlesource.com/857333

@jshin: Please confirm the issue and help in re-assigning if it is not related to your change.

Adding 'ReleaseBlock-Stable' label for M-68. Please feel free to remove if this is not applicable.

Thanks!

Comment 6 by gov...@chromium.org, Jul 23

Labels: -Target-67
We're not planning any further M67 releases, so removing "Target-67" label.

Comment 7 by js...@chromium.org, Jul 23

Labels: -Pri-1 Pri-3
Mergedinto: 854201
Status: Duplicate (was: Assigned)
This is not P1
►

Sign in to add a comment