This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28152 - FrameRequestCallback is not linked or defined
Summary: FrameRequestCallback is not linked or defined
Status: RESOLVED DUPLICATE of bug 29026
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://html.spec.whatwg.org/#the-win...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-06 10:49 UTC by contributor
Modified: 2015-08-31 14:51 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2015-03-06 10:49:33 UTC 
Specification: https://html.spec.whatwg.org/
Multipage: https://html.spec.whatwg.org/multipage/#the-window-object
Complete: https://html.spec.whatwg.org/#the-window-object
Referrer: 

Comment:
FrameRequestCallback is not linked or defined

Posted from: 14.162.102.1
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36 OPR/27.0.1689.76
Comment 1 Philip Jägenstedt 2015-03-06 10:53:12 UTC 
Used in long requestAnimationFrame(FrameRequestCallback callback);

The equivalent thing in Blink is:

callback interface RequestAnimationFrameCallback{
    // highResTime is passed as high resolution timestamp, see
    // http://www.w3.org/TR/hr-time/ for details.
    void handleEvent(double highResTime);
};
Comment 2 Anne 2015-08-28 10:02:30 UTC 
Blink seems incorrect as this should not be a callback interface.

*** This bug has been marked as a duplicate of bug 29026 ***
Comment 3 Philip Jägenstedt 2015-08-31 14:51:01 UTC 
Thanks, I'll add a TODO to Blink instead.