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

@mingyc commented on this pull request.



> +  <p><a for=list>For each</a> <a for="fetch group">deferred fetch record</a>
+  <var>deferredRecord</var> of <var>fetchGroup</var>'s
+  <a for="fetch group">deferred fetch records</a>:
+
+  <ol>
+   <li><p>Set <var>deferredRecord</var>'s <a for="deferred fetch record">invoke state</a> to
+   "<code>terminated</code>".
+
+   <li><p><a for=/>Fetch</a> <var>deferredRecord</var>'s
+   <a for="deferred fetch record">request</a>.
+  </ol>
+ </li>
+</ol>
+
+<p>When a <a for=fetch>fetch group</a> <var>fetchGroup</var> is
+<dfn export for="fetch group" id=concept-fetch-group-deactivate>deactivated</dfn>:

```
When a fetch group fetchGroup is deactivated:
```

There was a long privacy-related discussion about "whether a deferred request can be sent after navigating away and in BFCached" in https://github.com/WICG/pending-beacon/issues/3#issuecomment-1286397825, and I think the conclusion is that we need to look into the [`BackgroundSync Permission`](https://wicg.github.io/background-sync/spec/) (which is on by default in Chrome).

However, if the permission is off for the context, requests should not be sent out after user navigating away that context, as it may violate the user's expectation.

While `deactivated` covers broader than `BFCached after navigating away`, it is still relevant to this section

Should the above BackgroundSync-related behavior be specified here? It doesn't sound like an implementation-specific issue.

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

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