From 25b1702e423c81b517280ada43988830bcc9a3ad Mon Sep 17 00:00:00 2001 From: wbamberg Date: Fri, 10 Nov 2023 09:36:34 -0800 Subject: [PATCH] Explain why we're using XHR here --- .../api/file_api/using_files_from_web_applications/index.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/files/en-us/web/api/file_api/using_files_from_web_applications/index.md b/files/en-us/web/api/file_api/using_files_from_web_applications/index.md index 912687e5252978f..bdef04ce74fcd59 100644 --- a/files/en-us/web/api/file_api/using_files_from_web_applications/index.md +++ b/files/en-us/web/api/file_api/using_files_from_web_applications/index.md @@ -380,7 +380,11 @@ Here is a live demo of the code above: ## Example: Uploading a user-selected file -Another thing you might want to do is let the user upload the selected file or files (such as the images selected using the previous example) to a server. This can be done asynchronously very easily. +This example shows how to let the user upload files (such as the images selected using the previous example) to a server. + +> **Note:** It's usually preferable to make HTTP requests using the [Fetch API](/en-US/docs/Web/API/Fetch_API) instead of {{domxref("XMLHttpRequest")}}. However, in this case we want to show the user the upload progress, and this feature is still not supported by the Fetch API, so the example uses `XMLHttpRequest`. +> +> Work to track standardization of progress notifications using the Fetch API is at . ### Creating the upload tasks