- From: Noam Rosenthal <notifications@github.com>
- Date: Fri, 09 Jun 2023 00:47:25 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 9 June 2023 07:47:31 UTC
@noamr 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<Response> fetchLater(RequestInfo input, optional DeferredRequestInit init = {}); @annevk my current thinking about it is that when the timeout passes, we post a task to invoke the fetch to the document's event loop, without associating the task with the document. When that task is handled, we only flip the boolean and perform fetch if the document is not fully active. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1647#discussion_r1223964221 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1647/review/1471424318@github.com>
Received on Friday, 9 June 2023 07:47:31 UTC