Date Filter should support ISO Dates with sub-millisecond precision

[JohannesRudolph]

The docs for the date filter state that it supports ISO8601 date strings like yyyy-MM-ddTHH:mm:ss.SSSZ.

When passing a string that has a sub-millisecond component like yyyy-MM-ddTHH:mm:ss.SSSSZ (note the additional S) angular silently fails to format the date correctly.

Link to Fiddle: http://jsfiddle.net/yJddD/

Is this by design? And by the way, I think the documentation is wrong since fractional seconds are expressed with 'f' instead of 'S' according to http://de.wikipedia.org/wiki/ISO_8601

[mernen]

I've just tested (quick fiddle) on Firefox 17, Chrome 23, Safari 6, IE10. It seems they all accept an arbitrary number of decimal digits and truncate the number of milliseconds (except Safari will round up if you include this many 9's). However, looking at the ECMAScript 5 spec, this is not supported (they are pretty specific on 3 digits), so I'm not sure if AngularJS should support it…

Regarding Wikipedia's format, that seems to be just how German Wikipedia is describing the format, just like they're using "J" to represent the year. The W3C, for instance, uses merely "s" here, and ECMA-262 uses "sss".

[JohannesRudolph]

Thanks for this input. The reason this came up is because the server side of my application (Asp.Net MVC Web API) uses a default serialization format with more than three digits for the fractions of a second. I was able to work around it by overriding the default serialization format. It's a pity there's no JSON standard for date serialization, ideally...

[JohannesRudolph]

Revisiting this, I can confirm this is fixed in angular.js 1.2.4 (I can't say exactly when the fix was introduced btu it works).