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.

Sign up for GitHub

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

Jump to bottom

Support abort(reason) call on AbortController. #2889

Closed
gxtaillon opened this issue May 7, 2022 · 1 comment · Fixed by #4026
Closed

Support abort(reason) call on AbortController. #2889

gxtaillon opened this issue May 7, 2022 · 1 comment · Fixed by #4026
Labels
enhancement

Comments

@gxtaillon
Copy link

Motivation

Provide accurate error message when aborting fetch programmatically without user input.

Proposed Solution

Support abort(reason) call on AbortController.

Alternatives

None known to me.

Additional Context

Currently only abort() is supported. When using abort() on Chrome, cancelled fetch() calls return AbortError: The user aborted a request.. This is confusing when triggered without user input, for instance by timeouting early, or preemptively on navigation.

Best,
gxt
@ptdecker
Copy link

Up vote

@daxpedda daxpedda mentioned this issue Jul 29, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update AbortSignal and AbortController daxpedda/wasm-bindgen
2 participants
@ptdecker @gxtaillon