New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 874686 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Dec 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

icu-timezone-data is wrong for UTC-4

Project Member Reported by marchuk@chromium.org, Aug 15

Issue description

Chrome broswer version: 67 revision 541771 or higher
Case#: 16392286 

Description:
In  crbug.com/769706  we enabled icu-timezone-data by default, which is causing 
incorrect timezone detection for UTC-4.

Steps to reproduce: 
1. Set Windows timezone to any UTC-4, e.g. Santiago and turn off DST (e.g. if you live in U.S. Virgin Islands, which is in UTC-4 and has no daylight saving).
2. Reboot PC.
3. Navigate to https://toolbox.googleapps.com/apps/browserinfo/

Current Behavior / Reproduction: 
Observe "-3 GMT" on any chrome version after revision 541771

Expected Behavior: 
Observe "-4 GMT" on any version prior revision 541768

--js-flags="--no-icu-timezone-data" 
resolves the issue, but that's only workaround, issue here is that icu-timezone-data behaves not correctly.

This is causing bad user experience, as e.g. in chrome.png time of sent emails is in the future.

No issues on Internet Explorer/Edge.
 
chrome.png
130 KB View Download
windows_time.png
141 KB View Download
Status: Available (was: Untriaged)
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
Status: Archived (was: Available)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.

Sign in to add a comment