- From: Noam Rosenthal <notifications@github.com>
- Date: Mon, 08 May 2023 03:54:47 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 8 May 2023 10:54:53 UTC
> 1. "inactive timeout" -> "deferred delay". At least that seems clearer to me. But this is deferred delay specifically in the case of inactivity. "inactivity deferred delay"? > 2. I think `fetchLater` was quite nice in that it sorts the same as `fetch`. `fetchDeferred` could also work, though is a bit harder to spell. I don't think we need request in the name. > 3. It's not clear how the name fetch group states get activated. That needs some kind of additional PR against HTML I suppose? Yes, HTML would activate/deactivate in the BFCache code path. Need to prepare a PR for that but wanted to see that I'm on the right track first. > 4. I think we should describe the API in the same section as the fetch method. Could be called "Fetch methods" then. Will do > 5. Deferred fetching itself could then precede the "Fetch API" section. Maybe it could even be a subsection of "Fetching" though I don't mind a new top-level section. OK -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1647#issuecomment-1538171758 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1647/c1538171758@github.com>
Received on Monday, 8 May 2023 10:54:53 UTC