[Webkit-unassigned] [Bug 49963] New: V8 binding for DOMTimeStamp should be Number, not Date

[bugzilla-daemon at webkit.org]

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

           Summary: V8 binding for DOMTimeStamp should be Number, not Date
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit API
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jknotten at chromium.org


The W3C DOM Level 3 Core TR currently differs from standard practice in 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 ). 

Initially, I had thought that JSC in WebKit needed to change ( https://bugs.webkit.org/show_bug.cgi?id=49589 ), 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 an intention was made 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."

The action is here: http://www.w3.org/2008/webapps/track/actions/417

So, the V8 WebKit binding for DOMTimeStamp should be changed from Date to Number.

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