Closed
Description
https://fetch.spec.whatwg.org/#fetch-method has:
- Run the following in parallel:
- Fetch request.
- To process response for response, run these substeps: ...
- To process response done for response, run these substeps: ...
"process response" and "process response done" are defined as "Tasks that are queued by this standard are annotated as one of: ...", but they actually appear to be customization points within the Fetch algorithm for which the caller can provide an implementation. Assuming that's right, then:
- It doesn't make sense to say to run the fetch and its callbacks in parallel. Instead, we should run the fetch in parallel with the callbacks passed in.
- The callbacks need their defaults defined for when callers don't pass them in. I think the defaults are to be no-ops?
- The callbacks should be defined as customization points, not just annotations.