Move over an explainer to MSEdge repo so I can proceed to next step.

[guohuideng2024]

No description provided.

[guohuideng2024]

I named the explainer "explainer-for-loaf.md" because I expect more explainers could be added into this folder in future, and the future explainer can be named as "explainer-for-event-timing.md" etc

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a “Lightweight and Conditional Tracing” explainer document describing an extension to User Timing aimed at capturing conditional marks/measures for LoAF investigations.

Changes:

• Introduces a new explainer Markdown document for conditional tracing tied to LoAF.
• Documents proposed API surface (markConditional / measureConditional) and includes example usage.
• Adds initial Security/Privacy questionnaire responses for the proposed feature.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[guohuideng2024]

@sfortiner : The explainer has already been through WG discussion and passed. I am moving it here to comply MS requirement that the explainer must be in this repo.

Thanks for reviewing.

[Copilot]

Pull request overview

Adds an explainer document for a proposed “Lightweight and Conditional Tracing” mechanism intended to help developers attribute Long Animation Frames (LoAF) more precisely, by recording user-timing-like marks/measures only when a relevant performance incident occurs.

Changes:

• Introduce markConditional() / measureConditional() API concept and expected reporting surface (userTimingEntries on PerformanceLongAnimationFrameTiming).
• Provide sample JavaScript usage with PerformanceObserver and example outputs.
• Include initial alternatives discussion and Security/Privacy self-review questionnaire responses.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[aluhrs13]

@guohuideng2024 - Can you add this to the README too please?