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

@mingyc commented on this pull request.



> @@ -8481,6 +8615,75 @@ 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;
+};
+
+interface FetchLaterResult {
+  readonly attribute boolean sent;
+};
+
+partial interface mixin WindowOrWorkerGlobalScope {
+  [NewObject] FetchLaterResult fetchLater(RequestInfo input, optional DeferredRequestInit init = {});

Is it noop? Should we at least enforce `keepalive=true` in the spec?

Per similar API `navigator.sendBeacon()`'s [spec](https://www.w3.org/TR/beacon/), which explicitly says `The user agent MUST initiate a fetch with keepalive flag set ...` 

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

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