when change timezone by tzset, the getTimezoneOffset don't change until restart chromium
Reported by
zl200...@gmail.com,
May 11 2017
|
||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Steps to reproduce the problem:
1. open the webpage in attach ,and open your javascript console to see the output,
2. write another plugin to change timezone by linux function tzset, it will execute following line in browser process, (use plugin you can change timezone without restart chromium)
setenv("TZ", "GMT+3",1);
tzset();
3. refresh time_zone.html to check the value of getTimezoneOffset
What is the expected behavior?
1. if set to "GMT+3", it will output -180
2. if set to "GMT+4", it will output -240
What went wrong?
the value of getTimezoneOffset don't change when change timezone by plugin, only restart chromium it can output correct value
Did this work before? N/A
Chrome version: 54 Channel: n/a
OS Version: 3.14.28-1.10
Flash Version: Shockwave Flash 25.0 r0
,
May 16 2017
,
May 17 2017
Can you update to a more recent version of Chrome?
,
May 18 2017
,
May 18 2017
,
May 19 2017
I am afraid it will be a longtime to update to a recent version to test, as we compile chromium in our platform with special toolchain, if you know something about it, can you send me a patch for test?
,
May 19 2017
Thank you for providing more feedback. Adding requester "adamk@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 19 2017
Seems like more of a plugin issue than a JS issue, re-triaging.
,
May 20 2017
Thanks for your feedback, i know how to change the time now, there is a comment in time_zone_monitor_linux.cc, just use that way to inform time zone change.
// There is no true standard for where time zone information is actually
// stored. glibc uses /etc/localtime, uClibc uses /etc/TZ, and some older
// systems store the name of the time zone file within /usr/share/zoneinfo
// in /etc/timezone. Different libraries and custom builds may mean that
// still more paths are used. Just watch all three of these paths, because
// false positives are harmless, assuming the false positive rate is
// reasonable.
,
May 23 2017
AS it is plugin related issue could some one from dev team please look into this issue.Hence adding 'TE-NeedsTriageHelp' label. Thank you..!!
,
May 23 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ranjitkan@chromium.org
, May 12 2017