Re: DOMTimeStamp binding from Anne van Kesteren on 2009-02-12 (public-webapps@w3.org from January to March 2009)

From: Anne van Kesteren <annevk@opera.com>
Date: Thu, 12 Feb 2009 18:53:24 +0100
To: "Darin Adler" <darin@apple.com>, "Kartikaya Gupta" <lists.webapps@stakface.com>
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.uo82na0s64w2qv@annevk-t60.oslo.opera.com>

On Thu, 12 Feb 2009 18:51:02 +0100, Darin Adler <darin@apple.com> wrote:
> On Feb 12, 2009, at 7:08 AM, Kartikaya Gupta wrote:
>> Latest version of Chrome is still giving me a Date object. I don't know  
>> what version of WebKit it's using.
>
> Chrome uses an entirely different JavaScript binding, not the standard  
> WebKit one, so I'm not surprised that it’s exhibiting different behavior.

Would it be possible to make it bind to Date instead? That would be neat.  
(We are making other changes to the relevant specifications anyway.)


(Removing WHATWG since this is mostly relevant to DOM and Web IDL anyway.)


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>

Received on Thursday, 12 February 2009 17:54:21 UTC