Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) from isonmad on 2016-06-16 (public-webapps-github@w3.org from June 2016)

From: isonmad <notifications@github.com>
Date: Wed, 15 Jun 2016 18:58:26 -0700
To: whatwg/streams <streams@noreply.github.com>
Cc:
Message-ID: <whatwg/streams/issues/464/226369191@github.com>

> but we cannot revert .cancel()'s behavior now. It's already shipped. Too late.

You mean the implementation shipping [since Chrome 43](https://www.chromestatus.com/feature/4531143755956224), right? How many others have implemented it yet, aside from [IE10 shipping an incompatible API](https://www.chromestatus.com/feature/6605041225957376); is that not early enough for a breaking change still?

---
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/464#issuecomment-226369191

Received on Thursday, 16 June 2016 01:58:57 UTC