Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Check if fetch record's "fetch" instance needs to be nullable #1403

Open
noamr opened this issue Feb 14, 2022 · 0 comments
Open

Check if fetch record's "fetch" instance needs to be nullable #1403

noamr opened this issue Feb 14, 2022 · 0 comments

Comments

@noamr
Copy link
Contributor

noamr commented Feb 14, 2022

See https://github.com/whatwg/fetch/pull/1329/files#r737329884
The wording in fetch makes it seem that there could be cases where a fetch record can have a null reference to its corresponding fetch algorithm (or controller). Maybe it's not the case and it can be a strong reference.
@noamr noamr mentioned this issue Feb 14, 2022
Merged
3 tasks
annevk pushed a commit that referenced this issue Mar 14, 2022
@noamr
Return a fetch controller from the fetch algorithm
4561d5f 
This allows callers to perform certain actions on an ongoing fetch. Initially to abort or terminate it, and later on to conclude it.

This will eventually remove the need of using response as the object that retains timing info, as that creates certain ambiguities.

Corresponding Service Worker PR: w3c/ServiceWorker#1620.

Follow-up: #1403 and #1412.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@noamr