- From: Ming-Ying Chung <notifications@github.com>
- Date: Fri, 01 Sep 2023 00:58:58 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 1 September 2023 07:59:03 UTC
@mingyc 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; @noamr @fergald A followup question to the definition of our fetchGroup's `deactivated` state: In addition to the `freeze` Page LifeCycle event, should it also include `pause` event or not? Per https://html.spec.whatwg.org/C/#pause, no loads are allowed to start/continue in this state, and all background processing is also paused: `... require the user agent to pause while running a task until a condition goal is met` I would assume the answer is no, but would like to confirm. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1647#discussion_r1312701881 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1647/review/1606452875@github.com>
Received on Friday, 1 September 2023 07:59:03 UTC