Hi all, (If you do not work with readable byte streams, you can ignore this.)
We have recently landed the implementation <https://chromium-review.googlesource.com/c/chromium/src/+/3757034> of teeing support for readable byte streams in Blink based on the corresponding spec changes <https://github.com/whatwg/streams/pull/1114> to the Streams API standard. This improves standards compliance. Based on these changes, teeing a byte stream will now result in creating two readable byte streams, instead of two default readable streams. The implementation also now clones the chunks, instead of using the same ArrayBufferView, when teeing. This means that if you compare the output of the two streams, it’s possible to observe that the objects differ with the new behavior, which is demonstrated by the following script: const byteStream = new ReadableStream({ type: ‘bytes’ }); const [branch1, branch2] = byteStream.tee(); const { value: value1 } = branch1.getReader().read(); const { value: value2 } = branch2.getReader().read(); if (value1 === value2) { console.log('old behavior'); } else { console.log('new behavior'); } Cheers, Nidhi Jaju -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMZNYAM0D65zT6Q3Cpg0N%3Dk58L5t96JRRES%2BpBCOvXseL4SOBQ%40mail.gmail.com.
