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

Fetch confusion #63

Closed

annevk opened this issue Feb 8, 2023 · 1 comment

Assignees

Labels

fetch-based-api spec

annevk commented Feb 8, 2023

This is written as though Fetch were used as the underlying mechanism. However, since these are sent out-of-band, an implementation might not use the actual web-exposed Fetch API, and may instead use the underlying HTTP primitives directly.

That's not what fetch is. This has to use fetch and part of what this has to do as part of that is explain how policies get enforced.

annevk mentioned this issue

fetchLater() API (previously: PendingBeacon API) WebKit/standards-positions#85

Closed

mingyc added the spec label

clelland self-assigned this

mingyc added the fetch-based-api label

Collaborator

mingyc commented Nov 13, 2023

Addressed in whatwg/fetch#1647

mingyc closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment