design-reviews#1224: Incubation: Lightweight and Conditional Tracing for long animation frame timing API

#1224: Incubation: Lightweight and Conditional Tracing for long animation frame timing API

Visit on Github

Opened

Apr 28, 2026

Explainer

https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ConditionalTracing/explainer-for-loaf.md

The explainer

Includes the information requested by the Explainer Explainer.
Follows the Web Platform Design Principles.
Includes or links to answers to the Security/Privacy Questionnaire.
Describes user research you did to validate the problem and/or design.

Where and by whom is the work is being done?

GitHub repo:https://github.com/w3c/long-animation-frames
Primary contacts:
- guohuideng@microsoft.com
Organization/project driving the design: Microsoft and Google
This work is being funded by: Microsoft and Google
Incubation and standards groups that have discussed the design:
- github discussion: https://github.com/w3c/long-animation-frames/issues/3
- WebPerf WG minutes: https://docs.google.com/document/d/1M56DC5CweAcMCNd3yc_eDRuDNmfwcx3CQLRTWoMG4AM/edit?tab=t.0#heading=h.bpywm5gwk0li
Standards group(s) that you expect to discuss and/or adopt this work when it's ready: WebPerfWG

Feedback so far

Multi-stakeholder feedback:
- Chromium comments: planning to prototype this and work with the WebPerfWG.
- Mozilla comments: TBD
- WebKit comments: TBD
Major unresolved issues with or opposition to this design: N/A

You should also know that...

No response

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1224

Discussions

Comment by @xiaochengh Jun 10, 2026 (See Github)

Hi @guohuideng2024, the TAG reviewed this and fount it much more plausible than the previous approach. The overall mechanism looks highly feasible to us.

We have some comments at a lower level regarding the API design.

The proposed new APIs markCondition() and measureConditional() are directly tied to long animation frames, and therefore:
- The connection between these APIs and LoAF is not clear from the names and may be confusing
- This is not extendable to use cases like, e.g., we want to analyze long tasks instead of long animation frames, or if there are new types of performance incidents we want to introduce in the future
We are also unsure why we need to introduce "conditional" marks and measures, instead of somehow allowing existing marks and measures to be attributed to LoAF and similar incidents.