From 8d27e59a115aa9404af559087c68fbf4e66f4cb2 Mon Sep 17 00:00:00 2001
From: Alexander Petros <contact@alexpetros.com>
Date: Sun, 10 Nov 2024 23:18:05 -0500
Subject: [PATCH] Allow HTTP scheme fetches to make CORS preflight

This allows navigations to make CORS preflight requests, if the
navigation contains a request that is not safelisted. Navigation does
not (yet) provide APIs for non-safelisted requests; this update to the
fetch spec is a prerequisite for HTML spec changes that might add those
APIs (i.e. PUT method support in forms).
---
 fetch.bs | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/fetch.bs b/fetch.bs
index 6558d9414..94480af6f 100644
--- a/fetch.bs
+++ b/fetch.bs
@@ -5106,7 +5106,13 @@ steps:
     <p>When in doubt, return a <a>network error</a>.
 
    <dt><a>HTTP(S) scheme</a>
-   <dd><p>Return the result of running <a>HTTP fetch</a> given <var>fetchParams</var>.
+   <dd>
+    <ol>
+     <li><p>If <var>request</var>'s <a for=request>mode</a> is "<code>navigate</code>", then return
+     the result of running <a>HTTP fetch</a> given <var>fetchParams</var> and true.
+
+     <li><p>Return the result of running <a>HTTP fetch</a> given <var>fetchParams</var>.
+    </ol>
   </dl>
 
  <li><p>Return a <a for=/>network error</a>.