I am tagging this bug as a feature request, I am not sure about the exact component which it belongs.

This is very important for us. Because of this bug we are not using Chrome for our applications and we started to use other web browsers. Our first choice is Chrome but can not use now because it is displaying the Elektronik Funds Transfers time wrong.
Regards,
Mustafa Çiçek

Issue seems more like a feature request and hence marking it as untriaged.

Thanks!

 Issue 664099  has been merged into this issue.

This is an issue with our core timezone library, not a high-level feature request.

Passing ownership to jshin@, who seems to be responsible for ICU data updates and might know more about this.

It's a part of IETF timezone database 2016g. 

Chrome M56 has 2016h so that it's ok. Chrome M55 and M54 have 2016g so that they don't have this change. I missed 2016g.  


Let me update to 2016i (the latest) in M55 branch. 

If there's gonna be one more release in M54, we need to update M54 as well. 

Fixed in M56 and trunk. 

Requesting for merge to M55:  https://codereview.chromium.org/2507323002
The change is very safe. It's just updating the IETF timezone database to 2016i (the latest) that includes a Turkey timezone change. 

I'll ask for M54 merge soon. 

Requesting for merge to M54: https://codereview.chromium.org/2507323002

Again, this is very safe (just updating the IETF timezone database to 2016i). Without this change, Turkey time is off by one hour. 

[Automated comment] Request affecting a post-stable build (M54), manual review required.

Your change meets the bar and is auto-approved for M55 (branch: 2883)

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/buildspec/+/4e1eaa05ac9ee8240f99d2135dce350d7ac09c43

commit 4e1eaa05ac9ee8240f99d2135dce350d7ac09c43
Author: Jungshik Shin <jungshik@google.com>
Date: Fri Nov 18 00:29:14 2016

For M54, I have a ICU roll CL up to help review merge request. 
 https://chromereviews.googleplex.com/545847013

Thank you for M55 merge approval. 

How critical is the bug for M54? 

Don't think we have another stable refresh planned, users may need to wait until mid week of Dec for M55 roll out.

M55 folks ignore the RBS label. Its intended for efficient M54 triaging effort.

Thank you for the consideration, ligimole@. 

For people in Turkey, it'd be rather critical. It'll be the worst on Chrome OS because the OS clock is off by an hour. 

1. The time displayed at the lower-right corner will be off. 
2. Time stamps in the history page will be off by an hour.
3. Any Web sites relying on the client-side Javascript to show time will get the time  off by an hour. (gmail seems to be one of them. Google calendar is fine). 

On Chrome OS, all three are the case. On other platforms, #2 is certainly the case and #3 is likely to be the case (I have to check). 


We have about 3 weeks until M55 turns stable. Chrome's time has been off by an hour for about 3 weeks (since the end of October). 

How about this? Even though we're not likely to have an update for M55, it'd not hurt merging 'icu rolling cl' to buildpsec/branches/2840/DEPS  now, would it?  And if we happen to release yet another M54-stable (for another reason - e.g. an extremely critical security issue) or we decide that this issue is critical enough to release another M54 stable, we can get the fix (quickly). 
 

I should have noticed this change sooner (I thought I had subscribed to the IANA timezone announcement list, but it turned out that I hadn't replied to the verification email ....). 

Thanks Jessica for the clarification, we can proceed with the merge once the bug is verified either in canary/beta.I will loop Richard for merge approval.

Meanwhile can you also provide us with the steps to verify.

Thank you (btw, I'm jungshik at google :-)). 

The verification can be done with the following: 

In JS console, run the following. The result should be 3:00 instead 2:00.

(new Date("10/30/2016 12:00Z")).toLocaleString("en", {timeZone: "Europe/Istanbul"})
"10/30/2016, 3:00:00 PM"

An alternative to test: load the attached html and the alert box should show

"10/30/2016, 3:00:00 PM". 

When it's not fixed, it'd show 

"10/30/2016, 2:00:00 PM"

Deleted: turkeytz.html 239 bytes

turkeytz.html 239 bytes View Download

55.0.2883.59 was released with ICU rolled to 5e6ef0 ( https://codereview.chromium.org/2507323002 ). 

Richard, can you verify that it's fixed there?   See the previous two comments as to how to verify. 

Thanks 

We will get this verified in today's canary.

Thanks jshin@ for verification steps and test file.

Verified the fix on the latest canary(57.0.2926.0) and merge on the latest beta(55.0.2883.59) of Windows-10, Mac OS 10.11.6 and Linux Ubuntu 14.04. This is working as intended as per C#19(JS console output) and C#20(test file).

Attached is the screenshot of the same.

Deleted: 664126.png 31.9 KB

	664126.png 31.9 KB View Download

Thank you, ajha@ for the verification. 
Richard, could you consider merge request to M54? Thank you

 Issue 669048  has been merged into this issue.

This is too late for M54, but M55 will start rolling out to stable users this week and they'll see the fix then.

Yeah.. it's Nov 28. 

Sorry,  mustafa175@ and others in Turkey. It seems that you have to wait about a week for the stable release to have this fix (or switch to a beta channel).  

We wouldn't have released a new stable on the 11/23 either, the severity doesn't justify a new stable respin this late in the cycle.  The 11/9 release was the final M54 stable release.

Sorry to the folks affected!  As noted you can switch to Beta or Dev in the mean time, or wait for this fix to roll out with M55.

 Issue 659514  has been merged into this issue.

Remove obsolete labels.