new Date instance is interpreting ISODate incorrectly
Reported by
danjimen...@gmail.com,
Aug 13
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: 1. Create a variable with this format and day ocurring after 30. e.g. 2019-08-31 2. Create a new variable and instantiate a new Date class with the previous ISO date var as input. e.g. newDate = new Date(ISODate); 3. output date variable (in this case, newDate) What is the expected behavior? (Using the previous example) the date should be Sat Aug 31 What went wrong? (Using the previous example) the date is Fri Aug 30 Did this work before? N/A Chrome version: 68.0.3440.106 Channel: stable OS Version: 10.0 Flash Version: Example of error in fiddle https://jsfiddle.net/DannyBlast49/pf6bh02n/
,
Aug 14
Unable to reproduce the issue on Win-10 using chrome reported version #68.0.3440.106 and latest canary #70.0.3522.0. Attached a screen shot for reference. Following are the steps followed to reproduce the issue. ------------ 1. Navigated to https://jsfiddle.net/DannyBlast49/pf6bh02n/ 2. Observed that the date is Sat Aug 31. danjimenez123@ - Could you please check the issue on latest canary #70.0.3522.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Aug 16
,
Aug 16
Hello! Still encountering the error. See attached screenshots: [image: image.png] 2nd screenshot of Chrome version used. (Canary, 70.0.3524.0 64-bit). New profile created with all extensions (including default Google docs) disabled. Windows 10 Enterprise 64-bit. [image: image.png] Let me know if you need anything else.
,
Aug 16
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
,
Aug 17
danjimenez123@ Thanks for the update. Re-tested this issue on Windows 10 on the latest Canary 70.0.3524.0 and can still see the same behavior as mentioned in comment #2. Attached is the screen shot for reference. As per comment #4, Request you to attach the screen shots of the issue observed which will be helpful in further triaging. Thanks.. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by phanindra.mandapaka@chromium.org
, Aug 14