Status: New
Owner: ----
New issue 943 by [email protected]: Webkit data type binding for
DOMTimeStamp
http://code.google.com/p/v8/issues/detail?id=943
Hi, I'm trying to resolve a bug on WebKit:
https://bugs.webkit.org/show_bug.cgi?id=49589
Essentially the problem is that the WebKit V8 bindings generator binds
DOMTimeStamp to a Date object, while it seems that most other browsers bind
it to a Number. As mentioned in the bug report, it is per-spec to use the
Date object, but I was wondering it there was any other reason that the V8
binding was made to be a Date object?
From http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMTimeStamp, "For
ECMAScript, DOMTimeStamp is bound to the Date type because the range of the
integer type is too small."
WebKit's JSC binds DOMTimeStamp to a number (rather than an integer), which
according to ECMA 262 should be represented by a 64-bit double-precision
floating point number.
Is anything broken with the JSC and other browsers binding to Number, and
if not, perhaps we should consider trying to get the spec changed to from
Date to Number too?
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
