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

Re: [whatwg] DOMTimeStamp binding

From: Simon Pieters <simonp@opera.com>
Date: Thu, 12 Feb 2009 07:03:22 +0100
To: "Kartikaya Gupta" <lists.webapps@stakface.com>, "Darin Adler" <darin@apple.com>
Cc: whatwg@whatwg.org, public-webapps@w3.org
Message-ID: <op.uo75rwo1idj3kv@zcorpandell.linkoping.osa>

On Wed, 11 Feb 2009 21:14:44 +0100, Kartikaya Gupta <lists.webapps@stakface.com> wrote:

> 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?

Right now Web DOM Core says:

   A DOMTimeStamp represents a number of milliseconds. 

      typedef unsigned long long DOMTimeStamp;


...and then refers to WebIDL for what that means to ECMAScript.

-- 
Simon Pieters
Opera Software
Received on Thursday, 12 February 2009 06:04:10 GMT

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