Re: [whatwg/fetch] Deferred fetching (PR #1647)

@fergald commented on this pull request.



> + <li><p>Let <var>request</var> be <var>requestObject</var>'s <a for=Request>request</a>.
+
+ <li><p>Let <var>backgroundTimeout</var> be null.
+
+ <li><p>If <var>init</var> is given and <var>init</var>["<code>backgroundTimeout</code>"]
+ <a for=map>exists</a> then set <var>backgroundTimeout</var> to
+ <var>init</var>["<code>backgroundTimeout</code>"].
+
+ <li><p>If <var>backgroundTimeout</var> is not a {{DOMHighResTimeStamp}} then throw a {{TypeError}}.
+
+ <li><p>Let <var>deferredRecord</var> be the result of calling
+ <a>request a deferred fetch</a> given <var>request</var> and <var>backgroundTimeout</var>. This
+ may throw an exception.
+
+ <li>
+  <p><a for=AbortSignal lt=add>Add the following abort steps</a> to <var>requestObject</var>'s

`attempted` implies that some action (e.g. a network request) has been attempted. That's not true. All that has happened is that we've gone past the point where this request can be cancelled. Under the hood, the renderer process has told the browser process to make the request. It could have done nothing at all or it could have completed it. `committed` or `dispatched` mean exactly that, `pending` means the opposite (but would differ from the other 2 when cancelled).

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

Message ID: <whatwg/fetch/pull/1647/review/1576635925@github.com>