From 248494763766ccf164a2dc8dc9a1cd98fd2a1494 Mon Sep 17 00:00:00 2001 From: Rasmus Schultz Date: Mon, 5 Sep 2022 15:39:02 +0200 Subject: [PATCH] Encourage use of AbortController (#20315) * update old text with IE being officially dead, all major browsers support this API since 2019 * Update files/en-us/web/api/fetch_api/index.md Co-authored-by: Jean-Yves Perrier --- files/en-us/web/api/fetch_api/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/fetch_api/index.md b/files/en-us/web/api/fetch_api/index.md index 90382558dcec30a..660962d6d0fcfa5 100644 --- a/files/en-us/web/api/fetch_api/index.md +++ b/files/en-us/web/api/fetch_api/index.md @@ -46,7 +46,7 @@ The `fetch` specification differs from `jQuery.ajax()` in three main ways: ### Aborting a fetch -Browsers have started to add experimental support for the {{DOMxRef("AbortController")}} and {{DOMxRef("AbortSignal")}} interfaces (aka The Abort API), which allow operations like Fetch and XHR to be aborted if they have not already completed. See the interface pages for more details. +To abort incomplete `fetch()`, and even `XMLHttpRequest`, operations, use the {{DOMxRef("AbortController")}} and {{DOMxRef("AbortSignal")}} interfaces. ## Fetch Interfaces