Skip to content

Issues: whatwg/fetch

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

Clear current search query, filters, and sorts
20 Open 58 Closed
20 Open 58 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Can the set of safelisted methods be extended? clarification Standard could be clearer
#1774 opened Sep 19, 2024 by reschke
7
"should X be blocked" is a bad pattern clarification Standard could be clearer
#1714 opened Sep 29, 2023 by annevk
5
"Structured field value" isn't well defined clarification Standard could be clearer
#1672 opened Jun 14, 2023 by jyasskin
6
[Question] What is the expected behavior for reusing the Request body in a HTTP redirect fetch (status code 307 / 308)? clarification Standard could be clearer topic: streams
#1662 opened May 26, 2023 by ytxmobile98
4
If a resource allows credentials but omits Vary, shouldn't responses to non-CORS requests also contain Access-Control-Allow-Credentials? clarification Standard could be clearer topic: cors
#1601 opened Feb 2, 2023 by jub0bs
8
Can we consolidate initiator and initiator type? And potentially destination? clarification Standard could be clearer
#1563 opened Dec 9, 2022 by annevk
"set authorizationValue to authentication entry" is insufficiently precise clarification Standard could be clearer
#1497 opened Sep 30, 2022 by domenic
1
Consider if redirect tainting should apply to Timing-Allow-Origin clarification Standard could be clearer topic: timing Issues and PR that touch on the infrastructure that is used by ResourceTiming, NavigationTiming, etc
#1484 opened Sep 5, 2022 by noamr
3
Update Note on Request Destination / CSP directive clarification Standard could be clearer good first issue Ideal for someone new to a WHATWG standard or software project
#1466 opened Jul 6, 2022 by evilpie
4
Add initiatorType values to CSP/destination table clarification Standard could be clearer
#1452 opened Jun 14, 2022 by noamr
1
Editorial: find a new home for "fetch params" and friends clarification Standard could be clearer
#1340 opened Oct 22, 2021 by annevk
cleanup signal listener clarification Standard could be clearer
#1287 opened Aug 10, 2021 by ronag
9
What does "Assert" mean? clarification Standard could be clearer
#1277 opened Aug 3, 2021 by ronag
2
Explainer needed for creating requests clarification Standard could be clearer
#1143 opened Jan 20, 2021 by tabatkins
9
Align with post-payload HTTP terminology clarification Standard could be clearer topic: http
#1136 opened Jan 11, 2021 by annevk
2
Document header casing clarification Standard could be clearer topic: http
#972 opened Nov 26, 2019 by annevk
1
Clarification on CORS preflight fetches for TLS client certificates clarification Standard could be clearer topic: cors
#869 opened Feb 6, 2019 by sleevi
24
fetch() is unclear on which realm's Request it uses clarification Standard could be clearer
#777 opened Jul 12, 2018 by domenic
11
Cross-Origin-Resource-Policy advice clarification Standard could be clearer
#767 opened Jun 18, 2018 by annevk
2
Request.destination and the empty string clarification Standard could be clearer
#765 opened Jun 14, 2018 by a2sheppy
1
ProTip! Type g i on any issue or pull request to go back to the issue listing page.