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

Aborting: clarify usage for non-promise APIs #1040

Merged
merged 1 commit into from
Dec 6, 2021

Conversation

annevk
Copy link
Member

@annevk annevk commented Dec 6, 2021

Also clean up some remaining instances that didn't use signal.reason.

Closes #961.


Some changes here are copied from #1032 and some could be further improved in #1034. Given that those will likely take a bit more I figured we should at least get this clarified while people are updating their APIs to account for signal's abort reason.


💥 Error: 504 Gateway Time-out 💥

PR Preview failed to build. (Last tried on Dec 6, 2021, 9:57 AM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 HTML Diff Service - The HTML Diff Service is used to create HTML diffs of the spec changes suggested in a pull request.

🔗 Related URL

<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.

Also clean up some remaining instances that didn't use signal.reason.

Closes #961.
@annevk annevk added clarification Standard could be clearer topic: aborting AbortController and AbortSignal labels Dec 6, 2021
@annevk annevk requested a review from domenic December 6, 2021 09:55
@annevk annevk merged commit 982c7e2 into main Dec 6, 2021
@annevk annevk deleted the annevk/aborting-clarification branch December 6, 2021 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer topic: aborting AbortController and AbortSignal
Development

Successfully merging this pull request may close these issues.

Be clearer that not all aborting ends with an "AbortError" DOMException
2 participants