Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Editorial: initialize a response does not have an optional argument #1721

Merged
merged 1 commit into from
Nov 7, 2023
Merged

Editorial: initialize a response does not have an optional argument #1721

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions fetch.bs
View file
Open in desktop
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