- From: Domenic Denicola <notifications@github.com>
- Date: Mon, 10 Aug 2015 13:33:40 -0700
- To: whatwg/streams <streams@noreply.github.com>
Received on Monday, 10 August 2015 20:34:07 UTC
Hmm. A bit more concrete would be helpful. But for example, > For the templated tests, in the case of Errored, "ReadableStream (errored via call in start)" behaves different from "ReadableStream (errored via returning a rejected promise in start)" regarding "getReader() should return a reader that acts errored". This seems expected. For returning a rejected promise, you need to schedule a promise fulfillment callback to error the stream. Whereas calling error() will immediately error the stream. Once the stream becomes errored, you then reject the closed promise, which includes scheduling another microtask to call any registered handlers. So you can definitely observe differences here; the rejected-promise path is "more async" than the error() path. I wonder if it could be an issue with WebKit's promise implementation's timing? But it's kind of hard to tell without more detail... Happy to help if you can give me more to work with. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/390#issuecomment-129598198
Received on Monday, 10 August 2015 20:34:07 UTC