Skip to content

Commit

Permalink
Editorial: initialize a response does not have an optional argument
Browse files Browse the repository at this point in the history
  • Loading branch information
annevk committed Nov 7, 2023
1 parent 49bff76 commit 1df00b1
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions fetch.bs
Original file line number Diff line number Diff line change
Expand Up @@ -8192,8 +8192,7 @@ enum ResponseType { "basic", "cors", "default", "error", "opaque", "opaqueredire

<div algorithm>
<p>To <dfn>initialize a response</dfn>, given a {{Response}} object <var>response</var>,
{{ResponseInit}} <var>init</var>, and an optional <a for=/>body with type</a> <var>body</var>, run
these steps:
{{ResponseInit}} <var>init</var>, and null or a <a for=/>body with type</a> <var>body</var>:

<ol>
<li><p>If <var>init</var>["{{ResponseInit/status}}"] is not in the range 200 to 599, inclusive,
Expand All @@ -8213,7 +8212,7 @@ these steps:
<var>init</var>["{{ResponseInit/headers}}"].

<li>
<p>If <var>body</var> was given, then:
<p>If <var>body</var> is non-null, then:

<ol>
<li>
Expand Down

0 comments on commit 1df00b1

Please sign in to comment.