[whatwg] DOMTimeStamp in W3C Core 3
John Knottenbelt
jknotten at chromium.org
Tue Nov 23 02:52:12 PST 2010
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@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
More information about the whatwg
mailing list