Record timing info for promise resolve/reject and callback

[noamr]

• At least two implementers are interested (and none opposed):
  • Chromium (implemented)
  • Gecko (Long Animation Frame mozilla/standards-positions#929)
• Tests are written and can be reviewed and commented upon at:
  • Multiple tests in https://wpt.fyi/results/long-animation-frame/tentative?label=experimental&label=master&aligned test this.
• Implementation bugs are filed:
  • Chromium: already implemented
  • Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=1348405
  • WebKit: https://bugs.webkit.org/show_bug.cgi?id=270913
• MDN issue is filed: …
• The top of this comment includes a [clear commit message]

---

Preview | Diff

[saschanaz]

Maybe I lack the context, but having this in Web IDL covers a lot more than animation frames, right? Are the standards positions and implementation bugs actually cover the IDL layer change?

[noamr]

Maybe I lack the context, but having this in Web IDL covers a lot more than animation frames, right?

It does not, this is the shim between WebIDL and long animation frames. For long animation frames to report script timing it needs to know when particular scripts are enabled. This doesn't add anything web-observable to WebIDL directly.

Are the standards positions and implementation bugs actually cover the IDL layer change?

The explainers included the observable effect of this change as exposed by long animation frames from the start.