Chrome Has Inconsistent Date Objects from Year 1900-2020
Reported by
engp5567@gmail.com,
Nov 14
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: 1. With the latest Chrome, run code in JSBin: https://jsbin.com/jewohit/edit?html,js,console 2. Pay attention to Years: 1943-1945, and 1973-2020. They are different from the rest of years. 3. Use other browsers: Firefox, IE11, Edge, etc, run the same JSBin code. What is the expected behavior? All years should show the consistent results: YYYY 01 01; however, most Chrome's are wrong: (YYYY-1) 12 31, except those specific years mentioned above. What went wrong? All years from 1900-2020 should show the consistent results, like YYYY 01 01. All other browsers show the identical and correct results: YYYY 01 01. Did this work before? N/A Chrome version: 70.0.3538.102 Channel: stable OS Version: 10.0 Flash Version: Try similar code on CodePen; the same thing happens.
,
Nov 15
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 70.0.3538.102 using Windows 10 with the below mentioned steps. 1. Launched Chrome 2. Navigated to https://jsbin.com/jewohit/edit?html,js,console Observed the Date objects rendered correctly as expected. Attaching the screen cast of the same for reference. @Reporter: Could you please have a look at the screencast and let us know if we have missed anything in the process. Any further inputs from your end may be helpful.
,
Nov 15
I dug it a bit further; the reproducibility of this bug depends on your time zone. When you have to change the time zone in JSBin code from -07:00 to an hour ahead of your current time zone, you will see the inconsistency of the results. For example, if your time zone is - UTC-05:00 Eastern Time US and Canada, you have to modify the JSBin code from -07:00 to -04:00, then re-run the code. I am located at Pacific Standard Time (UTC-08:00), my colleague observed this bug 3 days after we shifted from Daylight Saving Time to Regular Time on Nov 3. Some senior customer's birthdays (earlier than 1987) can't be correctly displayed in Chrome, always a day behind the correct ones. I will upload a screen cast soon after I install such a software.
,
Nov 15
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 16
Confirmed, I see inconsistent output in this testcase as well in Chrome 70 on Linux, in US pacific time zone. Firefox does not show any consistencies.
,
Nov 16
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by phanindra.mandapaka@chromium.org
, Nov 14