-
Notifications
You must be signed in to change notification settings - Fork 55
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
Design review: AbortSignal.any() #737
Labels
Resolution: satisfied
The TAG is satisfied with this design
Review type: CG early review
An early review of general direction from a Community Group
Venue: WHATWG
Milestone
Comments
shaseley
added
Progress: untriaged
Review type: CG early review
An early review of general direction from a Community Group
labels
May 6, 2022
Hi there, We looked at this during a breakout today and we think this is ok — the addition does not introduce any new issues to the AbortSignal API. Thank you for working with us! |
Thanks all! |
This was referenced Apr 11, 2023
FYI: this feature has been merged into the dom spec (with no changes to the API since TAG review). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Resolution: satisfied
The TAG is satisfied with this design
Review type: CG early review
An early review of general direction from a Community Group
Venue: WHATWG
Braw mornin' TAG!
I'm requesting a TAG review of
AbortSignal.any(signals)
.AbortSignal.any(signals)
returns a signal that is aborted when any of the source signals are aborted. Developers can use this to combine independent abort sources, e.g. timeouts specified withAbortSignal.timeout()
and signals associated with user input, and pass them to async APIs likefetch()
.Further details:
We'd prefer the TAG provide feedback as (please delete all but the desired option):
🐛 open issues in our GitHub repo for each point of feedback
The text was updated successfully, but these errors were encountered: