`.getDate()` renders the incorrect date if followed by a 'T'.
Reported by
ryanpcmc...@gmail.com,
Jul 26 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2807.0 Safari/537.36 Steps to reproduce the problem: 1. Go here to see the unusual behavior: https://repl.it/CgDe 2. Or just run this from the console: console.log((new Date("2016-07-24T00:00:00")).getDate()); What is the expected behavior? That a 24 would be returned rather than a 23. What went wrong? `.getDate()` seems to reporting a different result than just `new Date()` or `Date.parse()`. Did this work before? N/A Chrome version: 54.0.2807.0 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 22.0 r0
,
Jul 29 2016
,
Jul 31 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 31 2017
The bug appears to have been fixed.
,
Aug 1 2017
Tested with Chrome 60 and it is indeed working. |
||||
►
Sign in to add a comment |
||||
Comment 1 by bokan@chromium.org
, Jul 26 2016Labels: -OS-Mac OS-All
Status: Untriaged (was: Unconfirmed)