New issue
Advanced search Search tips

Issue 914809 link

Starred by 2 users
Status: Duplicate
Merged: issue 854387
Owner: ----
Closed: Dec 19
Cc:
pastarmovj@chromium.org
js...@chromium.org
gsat...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Timezone Issue in RDS/Citrix mode

Reported by david.pa...@europcar.com, Dec 13 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. check the timezone of a RDS user session
2. timezone has to be the user local workstation timezone
3. but is not !

What is the expected behavior?
timezone has to be the user local workstation timezone, instead of the rds server local timezone

What went wrong?
timezone is not OK in a RDS/citrix user session with chrome 71.0..98 ...

It was OK in CHrome 71.0..80

please Check file attached

It's related to the timzeone new ICU bug.
other case opened earlier on the same subject : https://bugs.chromium.org/p/chromium/issues/detail?id=854387#c52

Did this work before? No 

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
Chome_Timezone_v68_v71.doc
357 KB Download

Comment 1 by dtapu...@chromium.org, Dec 13 

 Issue 914810  has been merged into this issue.

Comment 2 by dtapu...@chromium.org, Dec 13

Components: Blink>JavaScript>Internationalization

Comment 3 by susan.boorgula@chromium.org, Dec 14

Labels: Needs-Triage-M71

Comment 4 by david.pa...@europcar.com, Dec 14 

Hello all,

I made more tests this morning to try to understand what's going on.
Seems the Timezone issue occurs with Chrome 32Bits, not with Chrome 64Bits.

Whe a user is connected to a RDS/Citrix server, the user session timezone has to be the user local workstation timezone.
It's OK in other Browsers, like IE or Firefox, but seems problematic into Chrome since ICU timezone implementing in chrome v69...

One solution to solve the issue is to desactivate the new "ICU" timezone mode, with setting "--js-flags=--no-icu-timezone-data" in the chrome process start command line.

But would be better to solde that issue without the need of that "--js-flags=--no-icu-timezone-data parameter !!


Please find printscreens in the doc attached.


To resume :
Chrome 64Bits
71.0.3578.80   Timezone OK for australian users with or without “js-flags=--no-icu-timezone-data”.
71.0.3578.98   ?  need to make more tests.

Chrome 32Bits
71.0.3578.98 32Bits   « ICU » Timezone not OK at all.  Chrome Timezone is the RDS/citrix server timezone, instead of the user computer timezone !!
71.0.3578.80 32Bits   « ICU » Timezone OK for European Users, but not OK  for Australian users ( 1Hour difference ! )
68.0.3440.106 32Bits  No ICU ..  Timezone ok for all users

Can the ICU timezone issue be solved quickly ?

Regards,
David.
Chome_Timezone_v68_v71_20181214.doc
662 KB Download

Comment 5 by ajha@chromium.org, Dec 19

Cc: js...@chromium.org
Components: Enterprise
Labels: TE-NeedsTriageFromHYD

Comment 6 by jmukthavaram@chromium.org, Dec 19

Cc: pastarmovj@chromium.org
Labels: -TE-NeedsTriageFromHYD
Julien@, Could you please take a look into it.
Thanks!

Comment 7 by pastarmovj@chromium.org, Dec 19

Mergedinto: 854387
Status: Duplicate (was: Unconfirmed)
See https://bugs.chromium.org/p/chromium/issues/detail?id=854387#c58 for explanation about the regression reappearance.
►

Sign in to add a comment