From 4f0efd02396e920d7015832c3b6e52cde2542d0e Mon Sep 17 00:00:00 2001 From: Claudia Meadows Date: Fri, 4 Oct 2024 21:17:45 -0700 Subject: [PATCH] Remove reference to `mode: "websocket"` in `RequestInit` (#36200) In https://fetch.spec.whatwg.org/#request-class, there's an explicit note that this value is excluded from the `RequestMode` enum as it's not intended to be observable from JS. --- files/en-us/web/api/requestinit/index.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/files/en-us/web/api/requestinit/index.md b/files/en-us/web/api/requestinit/index.md index f2e33f1bb8e6712..70ba65ed8d8d36e 100644 --- a/files/en-us/web/api/requestinit/index.md +++ b/files/en-us/web/api/requestinit/index.md @@ -155,8 +155,6 @@ You can also construct a `Request` with a `RequestInit`, and pass the `Request` - : The request must be a [simple request](/en-US/docs/Web/HTTP/CORS#simple_requests), which restricts the headers that may be set to {{glossary("CORS-safelisted request header", "CORS-safelisted request headers")}}, and restricts methods to `GET`, `HEAD`, and `POST`. - `navigate` - : Used only by HTML navigation. A `navigate` request is created only while navigating between documents. - - `websocket` - - : Used only when establishing a [WebSocket](/en-US/docs/Web/API/WebSockets_API) connection. See [Making cross-origin requests](/en-US/docs/Web/API/Fetch_API/Using_Fetch#making_cross-origin_requests) for more details.