[w3ctag/design-reviews] User-defined script "entry points" for performance timing (Issue #1012)

こんにちは TAG-さん!

I'm requesting an early TAG design review of User-defined script "entry points" for performance timing.

"Long animation frames" help diagnose main-thread bottlenecks and attribute them to causes like scripts. However, for overhead reasons, we currently only report script "entry points" (platform callbacks, event listeners, script blocks, platform-promise resolvers) - which is often not granular enough. 

The proposal is to allow user code to define their functions as "entry points" that would be reported when attributing long animation frames.

  - Explainer¹: https://github.com/w3c/long-animation-frames/blob/main/user-defined-script-entry-point-explainer.md
  - User research: Since the inception of [long animation frames](https://w3c.github.io/long-animation-frames/), this has been the top issue that came back from adopters. See https://github.com/w3c/long-animation-frames/issues/3
  - Security and Privacy self-review²: [here](https://github.com/w3c/long-animation-frames/blob/main/user-defined-script-entry-point-explainer.md#security--privacy-self-review)
  - GitHub repo: https://github.com/w3c/long-animation-frames
  - Primary contacts: @noamr, Google; @tunetheweb, Google.
  - Organization/project driving the design: Google
  - Multi-stakeholder feedback³:
    - Chromium comments: planning to prototype this and work with the WebPerfWG.
    - Mozilla comments: TBD
    - WebKit comments: TBD
    - See [initial WebPerfWG discussion at TPAC](https://docs.google.com/document/d/1wL8Re4atVHVpfKTxhFfh8TNkkK4VCBbVJ-U70q5PWjo/edit?tab=t.0#heading=h.ri4hvc152s1h).

Further details:

  - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - The group where the incubation/design work on this is being done (or is intended to be done in the future): WebPerfWG
  - The group where standardization of this work is intended to be done ("unknown" if not known): WebPerfWG
  - Existing major pieces of multi-implementer review or discussion of this design:
  - Major unresolved issues with or opposition to this design: need to check if microtask support is feasible in all implementations.
  - This work is being funded by: Google



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1012
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1012@github.com>