toLocaleTimeString is wrong in some cases, compared to toTimeString
Reported by
justin.d...@zapier.com,
Oct 25 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Change your time zone to Sydney, Australia. 2. Open the attached HTML file. 3. Notice that the time returned from toTimeString is correct, but the time returned from toLocaleTimeString is incorrect by being one hour earlier. What is the expected behavior? toLocaleTimeString should return the correct time in all time zones. What went wrong? toLocaleTimeString is returning a time that is one hour earlier than it should be for Sydney, Australia. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 61.0.3163.100 Channel: n/a OS Version: OS X 10.12.6 Flash Version:
,
Oct 26 2017
Unable to reproduce this issue on reported version 61.0.3163.100, on latest stable 62.0.3202.62 and on latest canary 64.0.3250.0 using Mac 10.12.6 with below mentioned steps. Adding screencast of same. 1.Changed Timezone to Sydney-Australia 2.Naviagated to attached HTML and no deviation of times is seen. @Reporter: Could you please check whether we missed any steps and let us know so that we can triage it further. Thanks!
,
Oct 26 2017
Make sure to open the html file in a **new** tab. I should have mentioned that when you change the timezone, the tab already opened acts a little different with its own oddity. (toTimeString returns an abnormal result in that case.) Attached is a screenshot for comparison. 1. Upper left is using the same tab. 2. Upper right is using a new tab. 3. Lower left is Safari. 4. Lower right is Firefox.
,
Oct 26 2017
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 1 2017
Thanks for the update.. Unable to reproduce the issue in mac os 10.12.6 using chrome latest stable M62 #62.0.3202.75 and M64 #64.0.3255.0 . Followed the steps mentioned in comment #0 and #3.. Attached screencast for reference. @justin-- Could you please check in latest stable with a fresh chrome profile without any extensions and flags enabled and update us with your observations. Thanks!
,
Nov 3 2017
@hdodda It looks like this is working now (in both a clean profile and my normal profile), so something must have been fixed in the latest build. Neither of the behaviors I reported is happening now. ¯\_(ツ)_/¯
,
Nov 3 2017
Thank you for providing more feedback. Adding requester "hdodda@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
,
Nov 7 2017
As per comment #6, closing the issue as wontfix. Thanks...!! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by justin.d...@zapier.com
, Oct 25 201748.7 KB
48.7 KB View Download