This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Currently, we're using the Promise returned by the write() method for pacing write speed, i.e. just for flow control. As we've changed the Streams API to be more generic one, correlating error and each write() operation now is more meaningful. We already have awaitSpaceAvailable(). Let's just leave the functionality of flow control to it and have the Promise returned by the write() method be fulfilled only when that write() operation is finished. Not when the WritableStream can accept (buffer) more write() operations.
Fixed in ED.