-
Notifications
You must be signed in to change notification settings - Fork 323
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.
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
Author
Label
Milestones
Assignee
Sort
Issues list
Add syntax highlighting to code fragments
clarification
Standard could be clearer
#837
by annevk
was closed Dec 12, 2018
Proposal: New features or enhancements
needs implementer interest
Moving the issue forward requires implementers to express interest
topic: api
Response.json
helper
addition/proposal
#1389
by lucacasonato
was closed May 18, 2022
mixed content and CSP checks should be run after SW handles fetch event
#77
by wanderview
was closed Jul 14, 2015
Consider allow Service Worker to pass-through the original referrer
#89
by mfalken
was closed Jul 27, 2015
Developer-controlled streams for request/response
topic: streams
#88
by annevk
was closed Jan 17, 2017
Make the Response constructor throw when status is 101, 204, 205, or 304, and body is non-null
#86
by annevk
was closed Jul 23, 2015
Allow operation to outlive the document unloading (beacon)
#124
by kornelski
was closed Oct 13, 2016
redirecting from same-origin to cross-origin CORS with userpass should fail
#112
by wanderview
was closed Aug 20, 2015
need setHeaderFunction( request => newHeaders ) function called before request sent
#156
by bblfish
was closed Jul 22, 2016
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.