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.

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

chore: update "processing a manifest"'s signature #1058

Merged
merged 2 commits into from
Oct 31, 2022
Merged
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1248,8 +1248,8 @@ <h3>
<p>
The steps for <dfn data-export="" data-local-lt=
"processing">processing a manifest</dfn> are given by the following
algorithm. The algorithm takes [^link^] |el:HTMLLinkElement| and a
[=Response=] |response|.
algorithm. The algorithm takes [^link^] |el:HTMLLinkElement|, a
[=Response=] |response|, and a [=byte sequence=] |bodyBytes|.
</p>
<ol class="algorithm">
<li>Let |document URL:URL| be |el|'s [=Node/node document=]'s
Expand All @@ -1258,7 +1258,7 @@ <h3>
<li>Assert: |document URL:URL| is not null.
</li>
<li>Let |json| be the result of [=parse JSON bytes to an Infra
value=] passing |response|'s [=response/body=].
value=] passing |bodyBytes|.
</li>
<li>If the |json| is a parsing exception, or |json| is not an
[=ordered map=]:
Expand Down