Performance timeline - Long Animation Frames

[noamr]

WebKittens

@rniwa @smfr @achristensen07

Title of the spec

Long ANimation Frames API

URL to the spec

w3c/longtasks#122

URL to the spec's repository

https://github.com/w3c/longtasks/

Issue Tracker URL

No response

Explainer URL

https://github.com/w3c/longtasks/blob/main/loaf-explainer.md

TAG Design Review URL

w3ctag/design-reviews#911

Mozilla standards-positions issue URL

mozilla/standards-positions#929

WebKit Bugzilla URL

No response

Radar URL

No response

Description

Note that some of the comments on #52 apply also here, however since long animation frames don't directly expose the concept of tags this can arguably present some mitigation.

[noamr]

@rniwa @achristensen07 thoughts on this?

[smfr]

Can we please qualify the "Long frames" and "Long tasks" APIs with "Performance Timing", since they are not new APIs in their own right; they are just new types of PerformanceEntry.

[noamr]

Can we please qualify the "Long frames" and "Long tasks" APIs with "Performance Timing", since they are not new APIs in their own right; they are just new types of PerformanceEntry.

Fine with me, happy to change the title

[marcoscaceres]

@noamr is the intention to add this to an existing W3C spec? (If not happen already). Would it be better to do a review as a pull request there?

[tunetheweb]

Answering for @noamr who’s on annual leave at the moment.

This started off as part of the long tasks spec—hence the links in the original request in this issue.

However, it was felt it was better to pull this into its own spec as requested in w3c/longtasks#132. This work has been completed and it’s now available as it’s own spec (https://w3c.github.io/long-animation-frames/) and its own GitHub repo (https://github.com/w3c/long-animation-frames/).