New issue
Advanced search Search tips

Issue 711406 link

Starred by 7 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Chrome mobile returns wrong Timezone names for certain Timezones

Reported by qiushen...@gmail.com, Apr 13 2017

Issue description

Steps to reproduce the problem:
1. Open Chrome on any Android or iOS devices
2. Open any web page like google.com
3. Open JS Console
4. Run JS: console.log(Intl.DateTimeFormat().resolvedOptions().timeZone);
5. It outputs the best-guess Timezone.
6. Change device timezone manually to Beijing/Shanghai GMT+08:00
7. Run JS: console.log(Intl.DateTimeFormat().resolvedOptions().timeZone);
8. It outputs "America/Chicago" 

What is the expected behavior?
When mobile device timezone is set to GMT+08:00, Intl.DateTimeFormat().resolvedOptions().timeZone should return "Asia/Shanghai" or similar GMT+08:00 timezone names.

What went wrong?
When system uses "Asia/Shanghai" (China Standard Time - CST), Chome returns "America/Chicago" (Central Standard Time - CST) instead.

Did this work before? N/A 

Chrome version: 57.0.2987.132  Channel: stable
OS Version: 6.0.1
Flash Version: 

Chrome returns wrong timezone name when the mobile device sets to the following Timezone (list may not be complete):
· Atlantic Time (Barbados) GMT-04:00
· Buenos Aires GMT-03:00
· Beijing China GMT+08:00
· Cairo GMT+02:00
· Taipei China GMT+08:00

Same problem not reproducible on Chrome on Desktop. Problem only observed on Android and iOS systems.
 
Components: -Blink Blink>JavaScript>Internationalization
Status: Untriaged (was: Unconfirmed)

Comment 2 by habl...@google.com, Apr 19 2017

Labels: -OS-Android OS-All
Status: Available (was: Untriaged)
If this also happens on iOS it can't be V8?
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 19 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Sign in to add a comment