Fetch API Updates
WHATWG • Last updated 1 day ago
Activity Score
90/100- • Updated in the last week
- • 2 updates in last 30 days
- • Complete entries with dates, titles, URLs, and summaries
Recent Updates
Include end time & render-blocking in opaque responses
Include end time & render-blocking in opaque responses Resource Timing always includes `responseEnd` and `renderBlockingStatus`. Closes #1945.
Read more →Editorial: fix typos in deferred fetching quota section
Editorial: fix typos in deferred fetching quota section Closes #1948.
Read more →Add TAO destination check for navigation redirect chains
Add TAO destination check for navigation redirect chains Timing-Allow-Origin (TAO) currently only opts-in "backwards" in terms of origins and doesn't constitute an opt-in to the destination origin, which is the appropriate opt-in for navigations (contrary to subresources). This PR adds the mechanisms that can enable such "forward" opt-in, and can enable a navigation response to a redirect chain to know that the redirect chain opted in to expose the redirects to its origin. Tests: https://github.com/web-platform-tests/wpt/pull/60823 & https://github.com/web-platform-tests/wpt/pull/60873. Corresponding HTML PR: https://github.com/whatwg/html/pull/12513.
Read more →Add a textStream() method to the Body mixin
Add a textStream() method to the Body mixin Tests: https://github.com/web-platform-tests/wpt/pull/60356. Corresponding File API change: https://github.com/w3c/FileAPI/pull/221. Fixes #1861.
Read more →Define ABNF for origin-or-null
Define ABNF for origin-or-null The ABNF for Access-Control-Allow-Origin relies upon the origin-or-null syntax, which doesn't exist in RFC6454 (see https://www.rfc-editor.org/errata/eid3249). This patch defines the intended syntax.
Read more →Only consider pending fetch-later requests for deferred fetch quota
Only consider pending fetch-later requests for deferred fetch quota Quota computation shouldn't include aborted or already completed requests. WPT uses `AbortController` to ensure quota is freed up. This also makes sense, since they are no longer relevant. Therefore, only consider pending deferred fetches when computing quota.
Read more →Add WebDriver BiDi network logging with stable request IDs
Add WebDriver BiDi network logging with stable request IDs This PR is based on the feedback on #1540 as well as what was discussed in https://github.com/w3c/webdriver-bidi/issues/722. This introduces the concept of a stable WebDriver ID for requests, which is consistent across redirects, authentication attempts and CORS preflight. This also triggers steps from the WebDriver BiDi specification to emit network events and trigger data collection mechanisms. Co-authored-by: James Graham <james@hoppipolla.co.uk>
Read more →Add "text" destination type, for JavaScript text imports
Add "text" destination type, for JavaScript text imports See https://github.com/whatwg/html/pull/11933 for context.
Read more →Uniform Changelog API
Access WHATWG changelog updates through our uniform API. Same JSON structure across all sources — no adapter-specific parsing needed.
GET https://watchchangelog.com/api/v1/entries?source=fetch-api.updates{
"source": "fetch-api.updates",
"vendor": "WHATWG",
"id": "tag:github.com,2008:Grit::Commit/f1aff91b8bb3a0d3b38006c9d87119037aae766f",
"published_at": "2026-08-25T06:36:13.000Z",
"title": "Include end time & render-blocking in opaque responses",
"url": "https://github.com/whatwg/fetch/commit/f1aff91b8bb3a0d3b38006c9d87119037aae766f",
"summary": "Include end time & render-blocking in opaque responses Resource Timing always includes `responseEnd` and `renderBlockingStatus`. Closes #1945.",
"tags": [
"WHATWG",
"fetch-api.updates",
"http-client",
"web-standard",
"api"
]
}Get Your Free API Key
Sign up to access the full changelog API. All public sources are free — no credit card required.
Sign Up Free →Tags:
Related Sources
