New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 716167 link

Starred by 1 user
Status: WontFix
Owner:
adamk@chromium.org
Closed: Jun 2017
Cc:
rbyers@chromium.org
█ littledan@chromium.org
js...@chromium.org
gsat...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression

Blocked on:
issue 589858


Sign in to add a comment

Chrome 58 changed new Date("2017-04-07T19:03:46.357") response

Reported by sjw...@gmail.com, Apr 27 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
1. Open the console.
2. In chrome 58 Type `new Date("2017-04-07T19:03:46.357")`
3. See output is "Fri Apr 07 2017 19:03:46 GMT-0400 (Eastern Daylight Time)"
4. Type the same thing into chrome 57: `new Date("2017-04-07T19:03:46.357")`
5. See the output "Fri Apr 07 2017 15:03:46 GMT-0400 (EDT)"

What is the expected behavior?
I could expect the output to the same...

What went wrong?
"Fri Apr 07 2017 19:03:46 GMT-0400 (Eastern Daylight Time)" != "Fri Apr 07 2017 15:03:46 GMT-0400 (EDT)"

Did this work before? Yes 57

Chrome version: 58.0.3029.81  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 25.0 r0

Comment 1 by sjw...@gmail.com, Apr 27 2017 

On second thought... the way Chrome 58 behaves is how Firefox and IE behave. So this was probably a bug that was fixed not created in Chrome 58

Comment 2 by rbyers@chromium.org, Apr 27 2017

Blockedon: 589858
Cc: littledan@chromium.org
Components: -Blink Blink>JavaScript>Internationalization
Owner: adamk@chromium.org
Yes, I believe this is intentional: https://chromium.googlesource.com/v8/v8/+/d31c5410c4fdfc5eb66582892d5e3ecd3706bd58 -  issue 589858 

Did this break some website for you?  There's some discussion of some breakage of Google sites in issue 714301, but that's a Google-internal bug.  So let's keep the public discussion here?

Comment 3 by rbyers@chromium.org, Apr 27 2017

Cc: rbyers@chromium.org

Comment 4 by hablich@chromium.org, Apr 28 2017

Status: Assigned (was: Unconfirmed)

Comment 5 by hablich@chromium.org, Apr 28 2017

Labels: M-58

Comment 6 by sjw...@gmail.com, Apr 28 2017 

It did cause issues in chrome, but the same issues had been happening in every other browser, I just hadn't noticed before.

Comment 7 by adamk@chromium.org, Jun 12 2017

Status: WontFix (was: Assigned)
Marking as WontFix as this made it all the way M58 without getting reverted.
►

Sign in to add a comment