[Webkit-unassigned] [Bug 68769] New: [mac] Timestamp parameter to requestAnimationFrame is busted in USE(REQUEST_ANIMATION_FRAME_TIMER) path

[bugzilla-daemon at webkit.org]

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

           Summary: [mac] Timestamp parameter to requestAnimationFrame is
                    busted in USE(REQUEST_ANIMATION_FRAME_TIMER) path
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jamesr at chromium.org
                CC: simon.fraser at apple.com, cmarrin at apple.com,
                    nduca at chromium.org


The time parameter for requestAnimationFrame should be roughly equivalent to Date.now(), but in the USE(REQUEST_ANIMATION_FRAME_TIMER) path it has the wrong value.  This is because animationTimerFired() passes a double value from WTF::currentTime(), which is in seconds since the epoch, to serviceScriptedAnimations() which expects to receive a DOMTimeStamp, which should be an unsigned long of milliseconds since the epoch.

To convert the return value of WTF::currentTime() to a double you should use the helper convertSecondsToDOMTimeStamp()

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