- From: Adam Rice <notifications@github.com>
- Date: Mon, 06 Mar 2017 21:42:09 -0800
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 7 March 2017 05:42:43 UTC
Previously, calling abort() on a WritableStream or Writer would cause the sink abort() to be called immediately if the sink start() was still executing. This was inconsistent with the way write() and close() work and could be a cause of bugs. Postpone calling sink abort() until start() is complete. If start() errors, do not call abort() at all. Fixes #683. You can view, comment on, or merge this pull request online at: https://github.com/whatwg/streams/pull/688 -- Commit Summary -- * Do not call sink abort() while sink start() is running -- File Changes -- M reference-implementation/lib/writable-stream.js (28) M reference-implementation/web-platform-tests (2) -- Patch Links -- https://github.com/whatwg/streams/pull/688.patch https://github.com/whatwg/streams/pull/688.diff -- 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/pull/688
Received on Tuesday, 7 March 2017 05:42:43 UTC