Off by 1 for Date objects initiated with date strings of the format "YYYY-mm-dd"
Reported by
qdi...@gmail.com,
Oct 22
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Initialize a new Date object with a string such as "2018-01-01" 2. log the object 3. The object will have the preceding date instead of the date represented by the string. What is the expected behavior? It shouldn't be off by 1. What went wrong? It was off by 1. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 69.0.3497.100 Channel: n/a OS Version: 10.0 Flash Version:
,
Oct 23
Thanks for filing the issue! Able to reproduce the issue on reported chrome version 69.0.3497.100, latest stable 70.0.3538.67 and on the latest canary 72.0.3588.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.1 As the issue is seen from M60(60.0.3112.0) considering it as Non-Regression and marking it as Untriaged. Requesting someone from respective team to have a look in this for further inputs.
,
Oct 29
I think I was wrong about this. Chrome represents dates with the local timezone offset. So, for my timezone the offset is currently minus 5 hours (Central Daylight Time). If the string of "YYYY-mm-dd" is considered to be in ISO format with an implied time of T00:00:00.000Z, then the representation with the local timezone offset should show as a 5 hour offset into the previous day for my timezone. This issue may be closed so far as I'm concerned. Sorry I did not understand at the time of filing it as a bug.
,
Nov 9
|
|||
►
Sign in to add a comment |
|||
Comment 1 by phanindra.mandapaka@chromium.org
, Oct 22