New issue
Advanced search Search tips

Issue 852037 link

Starred by 3 users

Issue metadata

Status: Available
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

chrome://signin-internals uses ambiguous date format

Project Member Reported by wfh@chromium.org, Jun 12 2018

Issue description

Chrome Version: 69.0.3453.0 (Official Build) canary (64-bit) (cohort: Clang-64)
OS: Windows 10

What steps will reproduce the problem?
(1) Set date format in system settings to non-ambiguous ISO 8601 compliant e.g. YYYY-MM-DD
(2) Visit chrome://signin-internals
(3)

What is the expected result?

Dates are shown in non-ambiguous date format previously chosen.

What happens instead?

Dates are shown in ambiguous date format e.g. 6/11/18, which could mean 6th November 2018 or 11th June 2018.

N.B. chrome://sync-internals choses to use e.g. "Tuesday, June 11, 2018" which, while not respecting the system localization setting, is non-ambiguous.

Please use labels and text to provide additional information.

If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 

Comment 1 by msarda@chromium.org, Jun 15 2018

Labels: Hotlist-Polish

Comment 2 by msarda@chromium.org, Jun 15 2018

Owner: droger@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by msarda@chromium.org, Jun 15 2018

Labels: Hotlist-GoodFirstBug
This also occurs on Mac, regardless of my date format in System Preferences. Which is preferred, ISO 8601 or long-date format?

On chrome://sync-internals it always uses the long-date format while respecting the my device language, but doesn't take the system date format into account.
Project Member

Comment 5 by sheriffbot@chromium.org, Aug 3

Status: Available (was: Assigned)
--Chrome Identity automated triaging--

This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment