Positive: Long Animation Frame API

closes: #929

activities.json

@@ -910,6 +910,18 @@
     "title": "Lazy loading",
     "url": "https://html.spec.whatwg.org/multipage/urls-and-fetching.html#lazy-loading-attributes"
   },
+  {
+    "ciuName": null,
+    "description": "This specification defines APIs for reporting information for frames that take a long time to render.",
+    "id": "long-animation-frame-api",
+    "mozBugUrl": "https://bugzilla.mozilla.org/show_bug.cgi?id=1734997",
+    "mozPosition": "positive",
+    "mozPositionDetail": "This feature allows web developers to measure frame congestion and jank, and has a correlation with how user perceive this type of congestion. Web developers can use this API to improve the perceived performance of their pages.",
+    "mozPositionIssue": 929,
+    "org": "Proposal",
+    "title": "Long Animation Frame API",
+    "url": "https://w3c.github.io/longtasks/#sec-loaf-timing"
+  },
   {
     "ciuName": null,
     "description": "This document updates RFC 6761 with the goal of ensuring that \"localhost\" can be safely relied upon as a name for the local host's loopback interface. To that end, stub resolvers are required to resolve localhost names to loopback addresses. Recursive DNS servers are required to return \"NXDOMAIN\" when queried for localhost names, making non-conformant stub resolvers more likely to fail and produce problem reports that result in updates. Together, these requirements would allow applications and specifications to join regular users in drawing the common-sense conclusions that \"localhost\" means \"localhost\", and doesn't resolve to somewhere else on the network.",