Steps for attempt to populate the history entry's document seem to be missing a level of nesting

[ADKaster]

in https://html.spec.whatwg.org/multipage/browsing-the-web.html#attempt-to-populate-the-history-entry's-document, step 6 starts a global task on the navigation and traversal task source

Step 3 of the global task steps says:

If navigationParams is a non-fetch scheme navigation params, then set entry's document state's document to the result of running attempt to create a non-fetch scheme document given navigationParams.

So at this point, we've created a new document for the navigation history entry's document state using hand wavy implementation defined methods for non-fetch scheme urls.

Steps 4, 5, 6, and 7 then set a "failure" boolean to true in an "otherwise" chain. But then step 8 breaks the otherwise chain with a simple "If failure is true, then ...". Then we have a new set of otherwise statements that attempt to access the response of navigationParams. However, if navigationParams is a non-fetch scheme navigation params, it doesn't have a response.

I assume that after executing step 3, we are supposed to skip down to steps 13 and 14 to set the "ever populated" flag on the document, run the completion steps, and bail from the algorithm.

I'm not sure what a nice way to structure this is, but it seems to me like the current structure doesn't work because of the break in the if/else chain with step 8.

[ADKaster]

Related, in step 12 of attempt to populate the history entry's document what is request?

If entry's document state's request referrer is "client", then set it to request's referrer.

It seems out of place. Step 13 checks if entry's document state is non-null before manipulating it. As far as I can tell, there is no request in this algorithm at all.