[w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738)

Braw mornin' TAG!

I'm requesting a TAG review of Permissions-Policy: unload.

This is a proposal for a new [Permissions-Policy](https://github.com/w3c/webappsec-permissions-policy/blob/main/permissions-policy-explainer.md) entry that will disable unload handlers. Permissions-Policy is a mechanism for controlling individual page's access to features. This proposal would add a way for a page to opt out of firing unload handlers while allowing exceptions.

  - Explainer¹ (minimally containing user needs and example code): https://github.com/fergald/docs/blob/master/explainers/permissions-policy-unload.md

  - User research: currently only private feedback from sites that want to use this
  - Security and Privacy self-review²: https://github.com/fergald/docs/blob/master/explainers/permissions-policy-unload.md#self-review-questionnaire-security-and-privacy

  - Primary contacts (and their relationship to the specification):
      - Fergal Daly (fergald), Google - designing/specifying/implementing 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/5760325231050752


Further details:

  - [✓] 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): WHATWG
  - Existing major pieces of multi-stakeholder review or discussion of this design: https://github.com/w3c/webappsec-permissions-policy/issues/444

  - Major unresolved issues with or opposition to this design: https://github.com/w3c/webappsec-permissions-policy/issues/444#issuecomment-1047829132

  - 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 fergald rakina domenic

@rakina @domenic 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/738

You are receiving this because you are subscribed to this thread.

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

Received on Thursday, 12 May 2022 09:26:24 UTC