W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2010

[whatwg] DOMTimeStamp in W3C Core 3

From: John Knottenbelt <jknotten@chromium.org>
Date: Tue, 23 Nov 2010 10:52:12 +0000
Message-ID: <AANLkTimixD2ZsO_9AD8p0i2PofMWxw5nGbaFc3DbnPEw@mail.gmail.com>
I was recently tripped up by a difference between published the W3C
DOM Level 3 Core TR  and standard practice. The issue is that the TR
states that DOMTimeStamp should be bound to a Date object in
ECMAScript ( http://www.w3.org/TR/DOM-Level-3-Core/core.html#Core-DOMTimeStamp
).

But in practice, most existing implementations bind DOMTimeStamp to a
Number. This was observed on what-wg before:

http://www.mail-archive.com/whatwg at lists.whatwg.org/msg13626.html

And there is an intention to change the DOM Core 3 so that
DOMTimeStamp be bound to a number for ECMAScript:

http://www.w3.org/TR/DOM-Level-3-Events/#changes-DOMLevel2to3Changes

"Event.timeStamp is now a Number in the ECMAScript binding; a proposed
correction to make the same change in [DOM3 Core] is forthcoming."

and an action here:

http://www.w3.org/2008/webapps/track/actions/417

Can anybody hazard a guess as to when the  DOM Level 3 TR might be
updated with this change?

Many thanks

John
Received on Tuesday, 23 November 2010 02:52:12 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:28 UTC