Failure to parse date strings with timeone

[d3x0r]

new Date( "2018-07-23 09:53:16.752-07:00" );

The above results (in Edge console) [date] Invalid Date:

Firefox and chorme have supported this for 8+ years.

https://stackoverflow.com/questions/2182246/date-constructor-returns-nan-in-ie-but-works-in-firefox-and-chrome

new Date( "2018-07-23 09:53:16.752-07:00" );
new Date( "2018-07-23 09:53:16.752+07:00" );
// this one works - it's the only variant with timezone that does
new Date( "2018-07-23 09:53:16.752Z" );  

all of those work in Node, chrome, firefox, my C library that parses javascript times.

[MikeHolman]

@jackhorton FYI. Seems like this might be winglob/ICU issue?

[jackhorton]

Oops, completely missed this one. We actually use custom parsing for the date constructor (since I think the JS spec at least hints at the algorithm, if it doesn't define it outright), so this should be a problem regardless of the Intl implementation.