[Webkit-unassigned] [Bug 159038] New: [Mac] requestFrameAnimation callback timestamp should be very close to Performance.now()

[bugzilla-daemon at webkit.org]

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

            Bug ID: 159038
           Summary: [Mac] requestFrameAnimation callback timestamp should
                    be very close to Performance.now()
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Animations
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sabouhallawa at apple.com
                CC: dino at apple.com

The current implementation of requestFrameAnimation() passes the sum of timeUntilOutput and Performance.now() to the JS callback. timeUntilOutput is the difference between the outputTime and the now time which are passed to the CVDisplayLink callback. This addition causes the timestamp which is passed to the requestFrameAnimation() callback to be larger than the Performance.now() by almost 33 ms in the future.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160622/9a07bf52/attachment.html>