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

Editorial: Create the build a content range algorithm #1696

Merged
merged 1 commit into from
Aug 24, 2023

Conversation

dlrobertson
Copy link
Member

@dlrobertson dlrobertson commented Aug 22, 2023

Move the content-range algorithm to a standalone algorithm to avoid the additional inlined steps in Scheme fetch.

Fixes: #1552


Preview | Diff

fetch.bs Outdated

<li><p>Append <var>serializedFullLength</var> to <var>contentRange</var>.
<li><p>Let <var>contentRange</var> be the result of invoking <a>build a content range</a>
given <var>rangeStart</var>, <var>rangeEnd</var>, and <var>slicedBlob</var>'s {{Blob/size}}.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You go from serializedFullLength to serializedSlicedLength here. That seems wrong.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah! You are correct!

Move the content-range algorithm to a standalone algorithm to avoid the additional inlined steps in
Scheme fetch.
@annevk annevk merged commit f64d43f into whatwg:main Aug 24, 2023
1 check passed
@annevk
Copy link
Member

annevk commented Aug 24, 2023

Thanks!

@dlrobertson dlrobertson deleted the content-range branch August 24, 2023 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Move Content-Range header builder to separate algorithm
2 participants