- From: Mattias Buelens <notifications@github.com>
- Date: Wed, 03 May 2023 01:26:50 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 3 May 2023 08:26:59 UTC
@MattiasBuelens commented on this pull request. > +reason=]. Specifications should not [=AbortSignal/signal abort=], as that would interfere with the +normal use of this signal to respond to the stream being [=abort a writable stream|aborted=]. Agreed, "must not" would be better. Only the Streams standard itself should signal abort. However, since https://github.com/whatwg/dom/pull/1152 will make "to signal abort on an `AbortSignal`" private, it will no longer be possible for other specifications to affect this signal. So we can hopefully get rid of this entire footnote. 😁 By the way, should we already refactor Streams to use "to signal abort on an `AbortController`" instead? Or should we wait until https://github.com/whatwg/dom/pull/1152 has landed? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/pull/1277#discussion_r1183383673 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/streams/pull/1277/review/1410403184@github.com>
Received on Wednesday, 3 May 2023 08:26:59 UTC