27710 2014-12-27 20:10:19 +0000 FrameRequestCallback isn't defined (but is used) 2015-08-28 10:20:59 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED DUPLICATE 29026 https://html.spec.whatwg.org/#animation-frames P3 normal Unsorted 1 contributor ian annevk ian mike rainer.schuster contributor oldest_to_newest 116698 0 contributor 2014-12-27 20:10:19 +0000 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 116699 1 rainer.schuster 2014-12-27 20:11:37 +0000 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. 116850 2 ian 2015-01-06 22:43:40 +0000 Why? This spec obsoletes that spec, by request of that spec's editors. 116896 3 rainer.schuster 2015-01-07 19:26:32 +0000 (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. 116928 4 ian 2015-01-08 18:44:51 +0000 Oh, oops. That's supposed to be included. My apologies. 122842 5 annevk 2015-08-28 10:20:59 +0000 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 ***