Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editorial: account for removal of AbortSignal's follow #1277

Merged
merged 2 commits into from
May 8, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -6999,9 +6999,8 @@ above [=WritableStream/set up=] algorithm:
|stream|.[=WritableStream/[[controller]]=].[=WritableStreamDefaultController/[[signal]]=].
Specifications can [=AbortSignal/add=] or [=AbortSignal/remove=] algorithms to this
{{AbortSignal}}, or consult whether it is [=AbortSignal/aborted=] and its [=AbortSignal/abort
reason=]. Specifications should not [=AbortSignal/signal abort=] or make it [=AbortSignal/follow=]
another {{AbortSignal}}, as that would interfere with the normal use of this signal to respond to
the stream being [=abort a writable stream|aborted=].
reason=]. Specifications must 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=].

<p class="note">The usual usage is, after [=WritableStream/setting up=] the {{WritableStream}},
[=AbortSignal/add=] an algorithm to its [=WritableStream/signal=], which aborts any ongoing write
Expand Down