Neat!  Just a heads up that there is another active prototype in this area
right now
<https://groups.google.com/a/chromium.org/g/blink-dev/c/y3OkEzcrp24>.  (And
perhaps you would also be interested in helping review some of that work?)

On Thu, Feb 19, 2026 at 1:11 PM Chromestatus <
[email protected]> wrote:

> *Contact emails*
> [email protected]
>
> *Explainer*
>
> https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DocumentPolicy/DocumentPolicyInWorkers.md
>
> *Specification*
> https://github.com/WICG/js-self-profiling/pull/88
>
> *Summary*
> Allows js-profiling in dedicated workers This feature enables the
> JavaScript Self‑Profiling (js-profiling) API in Dedicated Workers, while
> remaining gated by Document Policy. It allows developers to obtain
> low‑overhead CPU attribution for JavaScript execution in workers, with
> Document Policy support for workers tracked separately.
>
> *Blink component*
> Blink>PerformanceAPIs
> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EPerformanceAPIs%22>
>
> *Web Feature ID*
> profiler <https://webstatus.dev/features/profiler>
>
> *Motivation*
> Modern web applications increasingly offload performance‑critical work to
> Dedicated Workers to keep the main thread responsive. While the JavaScript
> Self‑Profiling API provides low‑overhead CPU attribution for JavaScript
> execution, it is currently unavailable in workers due to its reliance on
> Document Policy, leaving developers without visibility into where CPU time
> is spent during background computation. Enabling js-profiling in Dedicated
> Workers fills this gap by allowing developers to capture representative
> JavaScript CPU profiles for worker execution, using the same explicit
> opt‑in and policy‑gated model already required for documents.
>
> *Initial public proposal*
> https://github.com/WICG/js-self-profiling/issues/33
>
> *Requires code in //chrome?*
> False
>
> *Tracking bug*
> https://issues.chromium.org/issues/482085416
>
> *Estimated milestones*
>
> No milestones specified
>
>
> *Link to entry on the Chrome Platform Status*
> https://chromestatus.com/feature/5159559872249856?gate=5181493867577344
>
> This intent message was generated by Chrome Platform Status
> <https://chromestatus.com>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69975252.050a0220.1f729.0da6.GAE%40google.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69975252.050a0220.1f729.0da6.GAE%40google.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEeF2TfYrHUTUY6vunNt_NgTpaEG_DPA2eAS6doZg-fdSN1p2Q%40mail.gmail.com.

Reply via email to