Intl.DateTimeFormat formats the date in the wrong timezone in some cases
Reported by
levdmit...@gmail.com,
Jan 11 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Change system time zone to the Moscow (UTC +3:00). I also reproduce it with (UTC +4:00) Baku 2. Just open https://jsfiddle.net/9ygfq19n/ or run in the console: var options = { hour: "numeric", minute: "numeric" }; var dateTimeFormat = new Intl.DateTimeFormat('en-US', options); dateTimeFormat.format(new Date('2012/05/14 12:13:14')); What is the expected behavior? "12:13 PM" What went wrong? "1:13 PM" Did this work before? N/A Does this work in other browsers? No MS Edge\IE11 - OK Mozilla FireFox - https://bugzilla.mozilla.org/show_bug.cgi?id=1330307 Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Jan 16 2017
Able to reproduce this issue on windows 10,Mac 10.12.2 using chrome stable M55-55.0.2883.87 and earlier version of chrome M30-30.0.1549.0. This is a non-regression issue and marking it as untriaged. Unable to reproduce this issue on Unbuntu 14.04 with same chrome version it has time has 12:13 PM Please look into the attached screencast. Thank You...
,
Jan 16 2017
,
Feb 15 2018
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
,
Feb 20 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by tkent@chromium.org
, Jan 11 2017