Wotcher TAG!

I'm requesting a TAG review of Pending API.

This is a proposal for Pending Beacon API. It is a system for sending beacons when pages are discarded, that uses a stateful API rather than having developers explicitly send beacons themselves.

• Explainer¹ (minimally containing user needs and example code): https://github.com/WICG/pending-beacon/blob/main/README.md
• User research: currently only feedback from RUM providers
• Security and Privacy self-review²: https://github.com/WICG/pending-beacon/blob/main/security-privacy-questionnaire.md
• GitHub repo (if you prefer feedback filed there): https://github.com/WICG/pending-beacon
• Primary contacts (and their relationship to the specification):
  • Ming-Ying Chung (mingyc), Google - designing/implementing in Chrome
  • Ian Clelland (clelland), Google - specifying in Chrome
• Organization/project driving the design: Google (BFCache team)
• External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5690553554436096

Further details:

• [✓] I have reviewed the TAG's Web Platform 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): WHATWG
• Existing major pieces of multi-stakeholder review or discussion of this design: https://w3c.github.io/web-performance/meetings/2022/2022-03-31/index.html
• Major unresolved issues with or opposition to this design: https://github.com/WICG/pending-beacon/issues
• This work is being funded by: Google

You should also know that...

[please tell us anything you think is relevant to this review]

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 @mingyc and @fergald