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

@annevk commented on this pull request.



> @@ -8449,6 +8597,60 @@ with a <var>promise</var>, <var>request</var>, <var>responseObject</var>, and an
 </div>
 
 
+<h3 id=fetch-later-method>FetchLater method</h3>
+
+<pre class=idl>
+
+dictionary DeferredRequestInit : RequestInit {
+  DOMHighResTimeStamp backgroundTimeout;
+};
+
+partial interface mixin WindowOrWorkerGlobalScope {
+  [NewObject] Promise&lt;Response> fetchLater(RequestInfo input, optional DeferredRequestInit init = {});

@fergald with regards to naming, yeah that is what I meant.

We should flip `FetchLaterState`'s boolean in at the start of the task that also dispatches `pageshow` in my opinion. The fetch might have already happened, but having a single synchronization point seems good and gives web developers a reliable API. (And doesn't encourage them to start polling.)

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

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