... I meant exactly what I said. This only concerns new Date(NaN).Message 1 of 2 , Jun 18, 2009View Source--- In email@example.com, "Jakob Kruse" <kruse@...> wrote:
> "new Date()" normally produces a perfectly ok Date object representing the current date and time. Does your change to ES5 mean that "JSON.stringify([ <any date object> ])" will produce "[null]"? And if not, why should it refuse to stringify the current date and time in this manner when other dates and times give meaningful results?I meant exactly what I said. This only concerns new Date(NaN).