'process a navigate fetch' doesn't load anything ever?

[smaug----]

https://html.spec.whatwg.org/#process-a-navigate-fetch 14.5.3 waits for some random(?) task to 'process response'.
But 'process response' links just to fetch itself being an option algorithm, and it wasn't provided when fetch was called.

[domenic]

So in general this is a casualty of two things:

• Fetch was refactored. It used to queue specific named tasks (these ones). Now it takes specific named callbacks (these ones). Many specs have not been updated, including HTML.

• The navigate algorithm has never had great fetch integration. In particular, the processing of response bodies is atrocious; it's done via algorithms like https://html.spec.whatwg.org/#read-html which say things like

  Each task that the networking task source places on the task queue while fetching runs must then fill the parser's input byte stream with the fetched bytes and cause the HTML parser to perform the appropriate processing of the input stream.

  The first task that the networking task source places on the task queue while fetching runs must process link headers given document, navigationParams's response, and "media", after the task has been procesed by the HTML parser.

The former of these I can look into fixing in #6315. The equivalent algorithm is https://whatpr.org/html/6315/browsing-the-web.html#create-navigation-params-by-fetching .

The latter of these is tracked by #8095.

[domfarolino]

I think this can be closed now, since the rewrite properly integrates with Fetch in the new "equivalent" algorithm: https://html.spec.whatwg.org/#create-navigation-params-by-fetching. But let me know if you think otherwise @smaug---- .