Issue metadata
Sign in to add a comment
|
Wrong result from getTimezoneOffset() in Turkish locale
Reported by
erol.mu...@gmail.com,
Nov 28 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36 Steps to reproduce the problem: While Locale Turkish, run the following commands: 1. (new Date(2006,11,26)).getTimezoneOffset() 2. (new Date(2006,2,22)).getTimezoneOffset() 3. (new Date(2006,2,29)).getTimezoneOffset() What is the expected behavior? 1. -120 2. -120 3. -180 What went wrong? the results was as follows: 1. -180 2. -240 3. -180 Did this work before? N/A Chrome version: 54.0.2840.99 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0
,
Nov 28 2016
I have tested the issue in Edge, Firefox and Chrome. Only Edge among them gives the right results. Firefox's results are also wrong: -180, -120, -180 respectively. I'm not familiar with the Chromium source code and I don't know how much getTimezoneOffset function relies on OS calls. IMHO, you probably will need a real Windows machine set to Turkish locale. A little info: Until 2016-10-29 Turkey's TZ was UTC+2 with daylight saving. Now it is UTC+3 with no daylight saving.
,
Nov 29 2016
The fix will be available in next stable release ~ 1 week from now. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rbyers@chromium.org
, Nov 28 2016Components: -Blink Blink>JavaScript>Internationalization