- From: fergald <notifications@github.com>
- Date: Mon, 11 Sep 2023 00:18:05 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 11 September 2023 07:18:11 UTC
@fergald commented on this pull request. > @@ -8485,6 +8618,92 @@ 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; > If that's the case, what's the point of this timeout at all? Perhaps we should spec & ship a substantially simpler version without it, and people can implement a regular timeout in userland? The point here you can't even do a reliable timer with userland + `backgroundTimeout`. With userland-only it's even worse. So the argument is to make this `timeout`, not `backgroundTimeout`. An uncacenlled fetch will activate on this timer whether the page is visible, invisible, frozen or in BFCache. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1647#discussion_r1321094841 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1647/review/1619282877@github.com>
Received on Monday, 11 September 2023 07:18:11 UTC