[webkit-dev] JSON.stringify(Date) losts the milliseconds information

[白石俊平]

> Please file a bug:

OK, I filed bug as:

https://bugs.webkit.org/show_bug.cgi?id=29063

and, I tested current implementations' behavior and attached test case.

thanks.

-shumpei

On Tue, Sep 8, 2009 at 9:36 PM, Eric Seidel<eric at webkit.org> wrote:
> Please file a bug:
> http://webkit.org/quality/reporting.html
> Ideally one which shows how our behavior differs from other browsers with a
> nice clear test case.
> -eric
> On Sun, Sep 6, 2009 at 10:30 PM, 白石俊平 <shumpei.shiraishi at gmail.com> wrote:
>>
>> Hi
>>
>> I tried to use the JSON.stringify() for Date object on Safari4 and
>> WebKit nightly build(48096), so I got result as follows.
>>
>> > JSON.stringify(new Date());
>> > 2009-09-07T04:49:43Z
>>
>> This result seems that milliseconds information of date is lost.
>> For some applications, millis info is important and this behavior may
>> be problem.
>>
>> And in the ECMAScript 5th specification, Date.toISOString() (this
>> function is called from Date.prototype.toJSON()) is defined as:
>>
>> ...Date Time string format (15.9.1.15). *All fields are present* in
>> the string...
>>
>> So, I think the Webkit's behavior should be treated as a bug, isn't it?
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>