W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Re: DOMTimeStamp binding

From: Kartikaya Gupta <lists.webapps@stakface.com>
Date: Wed, 11 Feb 2009 20:14:44 +0000
To: Darin Adler <darin@apple.com>
Cc: whatwg@whatwg.org, public-webapps@w3.org
Message-ID: <E1LXLUF-00044K-7H@bart.w3.org>

On Wed, 11 Feb 2009 10:58:00 -0800, Darin Adler <darin@apple.com> wrote:
> 
> On Feb 11, 2009, at 10:51 AM, Kartikaya Gupta wrote:
> 
> > Interesting. What version did you try on? I used Chrome 1.0.154.48  
> > and Safari 3.1 (525.13) on Windows.
> 
> The relevant version is the WebKit version rather than the Safari  
> version. They have separate version numbers.
> 
> I used WebKit/525.27.1 (the version that came with Safari 3.1.1) on  
> Mac OS X and also WebKit tip of tree on Mac OS X.
> 
> I also inspected the code and saw nothing that would create an object  
> in the JavaScript binding for this.
> 

I updated to Safari 3.2 on Windows (which looks it also has WebKit 525.27.1) and you're right, it is now showing "number" instead of "object". I guess this was changed not too long ago. So then my question is: why was it changed? And seeing as Opera, WebKit, and Gecko are in agreement now to return a number rather than a Date in ECMAScript, will the DOM 3 Core spec be updated? Or will this get rolled into Web DOM Core and/or HTML5?

Cheers,
kats
Received on Wednesday, 11 February 2009 20:15:23 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:30 GMT