[w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682)

Braw mornin' TAG!

I'm requesting a TAG review of State extension for JS Self-Profiling API.

Non javascript execution is hard to identify in traces captured with JS Self-Profiling API:
From a trace we cannot differentiate idle activity from top level UA activity, so for example code that triggers asynchronous rendering work cannot be measured properly.

  - Explainer¹: https://github.com/WICG/js-self-profiling/blob/main/markers.md

  - Security and Privacy self-review²: https://github.com/WICG/js-self-profiling/blob/main/markers.md#security-and-privacy-questionnaire

  - Primary contacts (and their relationship to the specification):
      - [Corentin Pescheloche] (@cnpsc), [Facebook] (editor)
      - [Andrew Comminos] (@acomminos), [Facebook] (editor)
  - Organization/project driving the design: Facebook
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status):
https://www.chromestatus.com/feature/5676352050036736


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): WICG
  - The group where standardization of this work is intended to be done ("unknown" if not known): unknown

You should also know that...
  - this is an extension of draft specification published by WICG: https://wicg.github.io/js-self-profiling/


We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify @cnpsc @acomminos


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