Issue metadata
Sign in to add a comment
|
File Manager displaying date in YYYY "M"MM D format
Reported by
kaingard...@gmail.com,
Mar 6 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9331.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3027.0 Safari/537.36 Platform: 9331.0.0 (Official Build) dev-channel swanky Steps to reproduce the problem: 1. Open File Manager 2. Observe file date format 3. Todays date (7 March 2017) is listed as 2017 M02 7 What is the expected behavior? Date should match system format for date - depending on locale. In Australia this is 07/2/2017 or 07 02 2017 What went wrong? Dates are formatted in non intuitive fashion Did this work before? N/A Chrome version: 58.0.3027.0 Channel: dev OS Version: 9331.0.0 Flash Version: 24.0.0.221 /opt/google/chrome/pepper/libpepflashplayer.so
,
Mar 7 2017
,
Mar 7 2017
,
May 11 2017
,
May 11 2017
,
May 12 2017
yamaguchi@, could you handle this? This is broken sometime in M58. I checked English (United Kingdom) and English (Australia) on ToT, but the issue did not reproduced.
,
May 12 2017
Reproduced on 60.0.3088.0 (developer build) on Chromebook Pixel, with language = English (Australia).
,
May 12 2017
,
May 12 2017
Setting Pri to 1 as we think this is likely to be affecting more than the Files app and Chrome OS.
,
May 12 2017
http://jsfiddle.net/mmfcL58z/2/ I could reproduce it in Chrome browser but only on the same machine as #7. It's likely to be caused when passing an empty list parameter passed Intl.DateTimeFormat constructor. Changing 'locales' to ['en-AU'] gives a result like "12 May 2017, 3:45 pm".
,
May 16 2017
Changing components because this is not specific issue on the Files app on Chrome OS as described in #10. Setting to Pri-2 for triage.
,
May 18 2017
Hi Dan, can you have a look? You touched ICU date recently. Maybe something broke there?
,
May 18 2017
Issue 722821 has been merged into this issue.
,
May 18 2017
,
May 18 2017
,
May 18 2017
I don't think this is related to 714301, because this issue is not about the timezone specification on the construction of a Date object, but about the i18n formatting of Date object.
,
May 23 2017
,
May 23 2017
jshin, can you take a look?
,
May 24 2017
Adam, this is the same as bug 722030 . Hmm...
,
May 24 2017
,
May 24 2017
,
May 27 2017
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/1c171759ebb6e1a50ff0c5efcec9f6073b22e62a commit 1c171759ebb6e1a50ff0c5efcec9f6073b22e62a Author: Adam Klein <adamk@chromium.org> Date: Sat May 27 21:40:43 2017 Revert "[intl] Fall back on an invalid default locale to "und"" This reverts commit 3059138b20bb56918cce24003832442c0ad701fa. TBR=littledan@chromium.org Bug: v8:6288 , chromium:698855 , chromium:720030 Change-Id: If4feb06c80f1f8f49c06ea6aeaffc8f1a072bdea Reviewed-on: https://chromium-review.googlesource.com/517182 Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/branch-heads/5.9@{#63} Cr-Branched-From: fe9bb7e6e251159852770160cfb21dad3cf03523-refs/heads/5.9.211@{#1} Cr-Branched-From: 70ad23791a21c0dd7ecef8d4d8dd30ff6fc291f6-refs/heads/master@{#44591} [modify] https://crrev.com/1c171759ebb6e1a50ff0c5efcec9f6073b22e62a/src/js/i18n.js
,
May 29 2017
Sorry for that bug, thanks for backporting the fix. I will try to stay more on top of these bugs; I was traveling around the time this was triaged.
,
Oct 24
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kaingard...@gmail.com
, Mar 6 2017402 KB
402 KB View Download