[whatwg/fetch] Add a destination type for FedCM (PR #1495)

We think it makes sense to define a destination type specific to FedCM requests (https://fedidcg.github.io/FedCM/)

This would replace the Sec-FedCM-CSRF header that is currently in the FedCM spec.

<!--
Thank you for contributing to the Fetch Standard! Please describe the change you are making and complete the checklist below if your change is not editorial.
-->

- [ ] At least two implementers are interested (and none opposed):
   * Chrome is interested (we're the ones proposing this)
   * Firefox is interested in FedCM [in general](https://mozilla.github.io/standards-positions/#fedcm) and has also suggested a change along these lines (https://github.com/fedidcg/FedCM/issues/320, though that issue is kind of meandering and has morphed into general CORS discussions)
- [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
   * I will add WPT tests once I update Chrome's implementation to use this destination
- [ ] [Implementation bugs](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) are filed:
   * Chrome: https://crbug.com/1368382
   * Firefox: n/a, fedcm impl still in progress
   * Safari: n/a, does not support fedcm
   * Deno (not for CORS changes): n/a

(See [WHATWG Working Mode: Changes](https://whatwg.org/working-mode#changes) for more details.)

You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/fetch/pull/1495

-- Commit Summary --

  * Add a destination type for FedCM

-- File Changes --

    M fetch.bs (5)

-- Patch Links --

https://github.com/whatwg/fetch/pull/1495.patch
https://github.com/whatwg/fetch/pull/1495.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1495
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1495@github.com>