Re: [whatwg/streams] Possible spec bug with concurrent byob reads (#1170) from James M Snell on 2021-10-04 (public-webapps-github@w3.org from October 2021)

From: James M Snell <notifications@github.com>
Date: Mon, 04 Oct 2021 11:19:31 -0700
To: whatwg/streams <streams@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/streams/issues/1170/933736575@github.com>

The behavior is also inconsistent when `autoAllocateChunkSize` is not used: 

![image](https://user-images.githubusercontent.com/439929/135902949-2c2a2f51-e3db-403b-b1f8-50a35ecd119e.png)

This is in edge, but also tested in chrome...

In the first read, the enqueue and subsequent respond appear to work. With the second read, we get an error saying that `c.byobRequest` is null.

It may very well be that this is just not the way to use the API, which is fine, but the spec and the documentation -- and likely the errors -- should be clearer on what the correct pattern should be.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/1170#issuecomment-933736575

Received on Monday, 4 October 2021 18:19:43 UTC