New issue
Advanced search Search tips

Issue 851910 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Wrong time output with momentJS

Reported by sta...@gmail.com, Jun 12 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0

Steps to reproduce the problem:
1. Open http://jsbin.com/bakaculavo/edit?html,js,output
2. The last line shows some weird output: "12:34 AM" instead of "1:00 AM" (my timezone is CET/UTC+1)

What is the expected behavior?
Please compare the output from this JSbin with other browsers like Firefox, IE11, Edge or Chrome 66, the output in each browser is the same except of Chrome 67. Until this version it worked as expected

What went wrong?
Strange timezone offset (?) added to date object, in the console you can see that the object "_d" in the moment object got the time "00:34:08" instead of "00:00:00"

Did this work before? Yes 66.0.3359.181

Chrome version: 67.0.3396.79  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 30.0 r0
 
Screen.jpg
215 KB View Download

Comment 1 by junov@chromium.org, Jun 12 2018

Components: -Blink Blink>HTML

Comment 2 by sta...@gmail.com, Jun 12 2018

Now I found out: if I change the year to 1900 it works again, even in Chrome 67. Seems its caused by the 0001 value, but why?
Labels: Needs-Bisect Needs-Triage-M67

Comment 4 by js...@chromium.org, Jun 12 2018

Status: WontFix (was: Unconfirmed)
In year 1, timezone offset WAS different from today. 


Sign in to add a comment