`AsyncContext` integration with web APIs
  • Past
  • Confirmed
  • Breakout Sessions

Meeting

Event details

Date:
Central European Summer Time
Status:
Confirmed
Location:
Triana - Level -1
Participants:
Andreu Botella, Rik Cabanier, Daniel Ehrenberg, Daniel Ehrenberg, Jonathan Kuperman, Michal Mocny
Big meeting:
TPAC 2023 (Calendar)

AsyncContext is a stage 2 TC39 proposal that allows propagating values across an async execution flow, much like Node.js's AsyncLocalStorage. However, when building this capability into the web platform we must consider the integration with web APIs – should setTimeout propagate the async context from the point it is called into the callback? What about event registration?

Furthermore, Chrome has been working on associating script-initiated actions from their causes further up the async call stack (tracking a task's attribution), which is useful browser-internally to enable metrics and web API improvements that would not be possible otherwise. Task attribution is the same as propagating browser-internal values across an async execution flow, so if we can ensure all of the task attribution use cases are covered by AsyncContext, the former could be built on top of the latter, in the specs and in browser engines.

Agenda

Chairs:
Andreu Botella, Daniel Ehrenberg

Description:
AsyncContext is a stage 2 TC39 proposal that allows propagating values across an async execution flow, much like Node.js's AsyncLocalStorage. However, when building this capability into the web platform we must consider the integration with web APIs – should setTimeout propagate the async context from the point it is called into the callback? What about event registration?

Furthermore, Chrome has been working on associating script-initiated actions from their causes further up the async call stack (tracking a task's attribution), which is useful browser-internally to enable metrics and web API improvements that would not be possible otherwise. Task attribution is the same as propagating browser-internal values across an async execution flow, so if we can ensure all of the task attribution use cases are covered by AsyncContext, the former could be built on top of the latter, in the specs and in browser engines.

Goal(s):
Get feedback from browser vendors and other interested parties as to which web APIs should propagate the async context.

Materials:

Export options

Personal Links

Please log in to export this event with all the information you have access to.

Public Links

The following links do not contain any sensitive information and can be shared publicly.

Feedback

Report feedback and issues on GitHub.