5 commits

Author	SHA1	Message	Date
Timothy Flynn	988df9cc8c	LibWeb: Perform writes during ReadableStreamPipeTo asynchronously ... I don't quite see what spec text requires this, but it is explicitly checked by WPT. We used to pass this test, but that regressed after commit 3c6010c663.	2025-04-14 16:56:15 -04:00
Timothy Flynn	6f6b39ecec	LibWeb: Import ReadableStreamPipeTo synchronous writing tests	2025-04-14 16:56:15 -04:00
Timothy Flynn	3c6010c663	LibWeb: Implement ReadableStreamPipeTo reads with less observability ... The spec states: Public API must not be used: while reading or writing, or performing any of the operations below, the JavaScript-modifiable reader, writer, and stream APIs (i.e. methods on the appropriate prototypes) must not be used. Instead, the streams must be manipulated directly. This migrates the default request request we were using to a custom read request which does not involve extra promises. I'm not sure about an analogous change with the way we write chunks to the receiving end. There isn't a "WriteRequest" utility to be used here, and no matter what AO we use, promises will be involved. Our current implementation at least does not seem to affect any tests.	2025-04-14 07:38:11 -04:00
Timothy Flynn	99550dc4ad	LibWeb: Import ReadableStreamPipeTo observability tests	2025-04-14 07:38:11 -04:00
Timothy Flynn	eb0a51faf0	LibWeb: Implement ReadableStreamPipeTo according to spec ... Our existing implementation of stream piping was extremely ad-hoc. It did nothing to handle closed/errored streams, and did not read from or write to streams in a way required by the spec. This new implementation uses a custom JS::Cell to drive the read/write loop.	2025-04-11 12:10:46 -04:00