Adam Rice

It's not landed yet: https://github.com/whatwg/encoding/pull/149/files#diff-ad08a062fe2c5f5084f74638410187daR1664 The TextEncoder step I copied it from: https://encoding.spec.whatwg.org/#ref-for-finished%E2%91%A1

This may be an unintended side-effect of supplying the CreateTransformStream() operation for specs to use rather than expecting them to create a _transformer_ object and pass it to the TransformStream...

I'm confused since according to the note: > There are other duplicate code points, but for those the first pointer is to be used. we should not be returning the...

Okay, I get it now. This change seems reasonable I think, but it won't be a high priority for Chrome.

I've concluded that (3) and (4) are very useful, and `close()` is also nice from an ease-of-use perspective, so I'm not going to remove `close()`.

Chrome supports if there is consensus. I don't want to be the only browser implementing this.

> 2022 update: Firefox shipped byte stream as of version 102, and it shipped Fetch with byte stream That's great news! It implies that it is web-compatible. We are currently...

> @yutakahirano Is Chrome open to reconsider its stance on implementing full duplex if we do the spec work & WPT tests? Yutaka no longer works on Chrome. My response...

The response is not sent until the request (including body) has been completely received. That's what I mean by "half-duplex". Smart people have been known to disagree about what the...

Sorry to show up towing a bikeshed, but how about ```idl unsigned long count(optional USVString key, optional USVString value); ``` allowing you to do ```js const p = new URLSearchParams('a=1&b=2&b=3&b=3');...