This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/ Multipage: https://html.spec.whatwg.org/multipage/#animation-frames Complete: https://html.spec.whatwg.org/#animation-frames Referrer: Comment: Reference to RequestAnimationFrame specification missing Posted from: 91.141.1.200 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
A reference to http://www.w3.org/TR/animation-timing/ or https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/RequestAnimationFrame/Overview.html should be added where RequestAnimationFrame is specified.
Why? This spec obsoletes that spec, by request of that spec's editors.
(In reply to Ian 'Hixie' Hickson from comment #2) > Why? This spec obsoletes that spec, by request of that spec's editors. The reason I opened this bug was that the html specification defines in the Window interface: long requestAnimationFrame(FrameRequestCallback callback); void cancelAnimationFrame(long handle); but FrameRequestCallback (which is used) is specified only externally, so the specification is somehow incomplete. The definition callback FrameRequestCallback = void (DOMHighResTimeStamp time); is missing.
Oh, oops. That's supposed to be included. My apologies.
This ended up getting fixed in a newer report. Sorry for not spotting it was a duplicate of your report. *** This bug has been marked as a duplicate of bug 29026 ***