Frank can you take a look?

We use citrix PVS with a GoldenImage streamed to multiple vmware vm, with windows 2012R2 & xenapp 7.15 LTSR.
We made a GoldenImage version rollback, because of this Timezone issue, to be bach in Chrome V68.
Our australian users had 11h of time difference.
Our German users have 2hours of time difference.

Issue only occurs in Google Chrome since version 69.
No issue in IE or Firefox.

Our servers are located in a datacenter in france, near Paris.
We are using a BlueCoat proxy service in the cloud, which public IP seems to be located in UK.

Regards,

Thanks for filing the issue!

Tried checking the issue on reported chrome version 69.0.3497.100 and on the previous stable 68.0.3440.106 using Windows 10 with the below mentioned steps.
1. Launched Chrome
2. Inspected the page -> Console
3. Pasted -> javascript:new Date().toString()
We observed similar console output in both the mentioned M68 & M69 versions. Attaching the screen shot of the same for reference.

@david.pauchet: Could you please have a look at the screen shot and let us know if we have missed anything in the process.

Deleted: 891206.png 1.1 MB

	891206.png 1.1 MB View Download

We do not have the issue on our "local computer chrome browser".
No issue on Win7 and Win10 "local" computers.

Issue only occurs on our RDS/Citrix servers.
2 citrix farms impacted : 
first one is an old one, with Windows 2008R2 & Xenapp 6.5
second one is a new one, with Windows 2012R2 & Xenapp 7.15 LTSR
Both server farms are located in the same datacenter, and use same internet proxy.

Same issue on both farms since Chrome V69 upgrade.
We had to rollback to V68.

"Local" computers do not use the same internet access/proxy than the one used by servers into the datacenter.

How does the Chrome Browser get the user session timezone ?
Is there any modification on that side in chromeV69 ? a new way to get that timezone information ?

is Google CHrome now taking the Proxy timezone as reference, instead of the user windows session timezone ?

Regards,
David.

 

Thank you for providing more feedback. Adding the requester to the cc list.

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

Hello,

I made some additionnal tests to try to understand this behaviour, since Chrome V69 upgrade.

Please find attached a doc. with explanations and printscreens.

Seems that, since Chrome V69 upgrade, Chrome take the server default TimeZone as TimeZone, instead of the RDS/ICA windows User session TimeZone.

It was OK with Chrome v68.

Deleted: Chome_Timezone_v68_v69_2.doc 547 KB

Chome_Timezone_v68_v69_2.doc 547 KB Download

As per comment#6 the issue seems to occur only on RDS/Citrix servers, but not on local computers, hence forwarding it to Inhouse to check the same on the specified Environment. Adding label "TE-NeedsTriageFromHYD" for further investigation from respective team.

Thanks! 

Hello Guyz,
are you able to reproduce the issue ?

Thanks,
David.

Unable to test this issue on Citrix Xendesktop 7.9, due to non-availability of steaming image test setup, hence adding untriaging label & requesting dev team to look into this issue.

@Julian,
Could you please take a look into it.
Thanks..!

Yang, can you please advice if this is a V8 issue or Chrome issue?

This doesn't ring a bell. Ulan or Jungshik may know.

Since Chrome 67 V8 uses ICU backend for timezone computation.

Maybe there were changes in ICU? Deferring this to Jungshik.

The ICU change is most visible on very historical dates. It sounds like the change here might have to do with how Chromium gets the timezone from the OS; I don't know if there were recent changes there.

https://chromiumdash.appspot.com/schedule show branch off date for 68 is May 24 and 69 is July 19. So the change is likely landed between May 24 and July 19. 
I saw one suspect

https://chromium.googlesource.com/chromium/deps/icu.git/+/172d33141cd16df9d027cfd49bfe940b1dc66f1a

jshin@chromium.org - could you take a look at this?

Hello All,

Timezone Issue solved with Chrome V72 Canary.

Related post there : https://bugs.chromium.org/p/chromium/issues/detail?id=854387&can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=

Regards,
David.

Deleted: Chrome_Canary72_Timezone.jpg 160 KB

	Chrome_Canary72_Timezone.jpg 160 KB View Download

Hi all,

Tested with latest v71 just released ( 71.0.3578.80 Official Build ), and Timezone is OK in RDS mode without the ""--js-flags="--no-icu-timezone-data" parameter in the command line.

Chrome Timezone is now the user RDS session timezone.

Thanks for helping & resolving this issue.
David.

Hello all,

RDS timezone issue seems to be corrected with latest version 71.

But i get now an issue with my australian users timezone, with 1hour difference between v68 time and v71 ICU time !

Need to rollback one more time to Chrome V68, latest well known version without timezone issues in RDS/ICA mode.