[whatwg/fetch] Editorial: Use controller for redirect navigation (PR #1469)

Remove the existing navigation redirect, and allow the caller
to use the controller to continue to the next redirect.

This simplifies the navigation HTML<->FETCH flow, as now there is
a single `fetch params` struct for the course of the entire navigation.
Up until now some data from fetch params would be lost, like timing info
and task desination, because navigation fetches create a brand new
`fetch params` struct. Now that data is retained, and the only thing that
HTML needs to do is call `process the next redirect` on the fetch controller.

<!--
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):
   * …
   * …
- [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
   * …
- [ ] [Implementation bugs](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) are filed:
   * Chrome: …
   * Firefox: …
   * Safari: …
   * Deno (not for CORS changes): …

(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/1469


-- Commit Summary --

  * Editorial: Use controller for redirect navigation

-- File Changes --

    M fetch.bs (38)

-- Patch Links --

https://github.com/whatwg/fetch/pull/1469.patch

https://github.com/whatwg/fetch/pull/1469.diff


-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1469

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

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