[Webkit-unassigned] [Bug 49589] DOMTimeStamp needs to be bound to Date object in ECMAScript

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Nov 17 06:58:30 PST 2010


https://bugs.webkit.org/show_bug.cgi?id=49589





--- Comment #3 from John Knottenbelt <jknotten at chromium.org>  2010-11-17 06:58:30 PST ---
Out of Opera, Firefox, Safari, and Chromium, it seems that right now only Chromium binds it to a Date object. 

I tried to check on IE, but my test script failed as the onload event did not have a timeStamp field.

The ECMAScript 262 specification for Date says that the valueOf() method of Date should return "the Number, which is the time value". This means that code that works with the DOMTimeStamp as if it were a number should continue to work (even if it is a Date instance). I use this fact in my test https://bugs.webkit.org/show_bug.cgi?id=48518 where I check that Geoposition timestamps are well-formed.

Since this change affects only Mac WebKit, it would be great if you could suggest next steps on this issue.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list