You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think I have just found a timezone database parse(?) error.
Moment
moment('1890-01-01T00:00:00Z').clone().tz('Europe/Paris').format()// "1890-01-01T00:09:21+00:09" // CORRECTmoment('1890-01-01T00:00:00Z').clone().tz('Europe/Budapest').format()// "1890-01-01T01:00:00+01:00" // WRONG// It should be "1890-01-01T01:16:20+01:16"
Zone NAME GMTOFF RULES FORMAT [UNTIL]
Zone Europe/Budapest 1:16:20 - LMT 1890 Oct
It means, the tzdb is correct.
I guess the JS code is also correct and the tzdb parser should be fixed (cause 'Europe/Paris' time-zone is well-parsed).
Environment:
Chrome 55 on Ubuntu 14.04.5 LTS
System timezone: Europe/Budapest
console.log((newDate()).toString())// Sun Feb 26 2017 11:19:46 GMT+0100 (CET)console.log((newDate()).toLocaleString())// 2017. 02. 26. 11:19:46console.log((newDate()).getTimezoneOffset())// -60console.log(navigator.userAgent)// Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36console.log(moment.version)// 2.17.1
The text was updated successfully, but these errors were encountered:
Description of the Issue and Steps to Reproduce:
I think I have just found a timezone database parse(?) error.
Moment
Java DateTime API
From the tzdb-2016j:
It means, the tzdb is correct.
I guess the JS code is also correct and the tzdb parser should be fixed (cause 'Europe/Paris' time-zone is well-parsed).
Environment:
Chrome 55 on Ubuntu 14.04.5 LTS
System timezone: Europe/Budapest
The text was updated successfully, but these errors were encountered: