LibWeb/Streams: Actually implement the piped through steps

This mistakenly implemented the 'piped to' operation on ReadableStream.
No functional difference as the caller was doing the extra work already
of 'piped through' vs 'piped to'.
This commit is contained in:
Shannon Booth 2024-12-26 12:02:07 +13:00 committed by Tim Flynn
parent a28961a92d
commit ffda698d3a
Notes: github-actions[bot] 2024-12-27 14:57:36 +00:00
3 changed files with 14 additions and 9 deletions

View file

@ -744,9 +744,7 @@ void fetch_response_handover(JS::Realm& realm, Infrastructure::FetchParams const
transform_stream->set_up(identity_transform_algorithm, flush_algorithm);
// 4. Set internalResponses bodys stream to the result of internalResponses bodys stream piped through transformStream.
auto promise = internal_response->body()->stream()->piped_through(transform_stream->writable());
WebIDL::mark_promise_as_handled(*promise);
internal_response->body()->set_stream(transform_stream->readable());
internal_response->body()->set_stream(internal_response->body()->stream()->piped_through(transform_stream));
}
// 8. If fetchParamss process response consume body is non-null, then: