New issue
Advanced search Search tips

Issue 686665 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

toLocaleTimeString offsets time by 39 minutes and 21 seconds for Brussels timezone (+1)

Reported by da...@tuppeny.com, Jan 30 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. Set timezone to GMT
2. Run this in browser console:
  new Date('1900-12-30T15:30:00-0100').toLocaleTimeString()
3. Output is:
  16:30:00

4. Set timezone to Brussels (+1)
5. Run this in browser console:
  new Date('1900-12-30T15:30:00-0100').toLocaleTimeString()
6. Output is:
  16:39:21

What is the expected behavior?
I expected the output time to be
  ‎17‎:‎30‎:‎00

In Edge, I get the expected output, though strangely Firefox also returns 16:39:21! We can't come with any explanation for this result.

What went wrong?
The time returned was shifted by 36 minutes and 21 seconds but we expected 1 hour.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 55.0.2883.87  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0
 

Comment 1 by da...@tuppeny.com, Jan 30 2017

Jon Skeet sent me this link:

https://github.com/eggert/tz/blob/master/europe#L1282

Which shows that Paris time (which is lumpoed with Brussels in Windows timezones) was indeed 9:21 out for a period so it's very likely this is actually working as expected (we were unable to find any data on this ourselves).
Labels: Needs-Milestone
Components: Blink>JavaScript>Internationalization
Adding a component, though I am not sure about it at all.
Status: WontFix (was: Unconfirmed)
Closing according to #1.

Sign in to add a comment