Providing an `AbortSignal` instead of calling .abort()
Open
Nobody has claimed this yet.
Future Candidate Feature
- Dominant language
- HTML
- Stars
- 510
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
It would nice, in a future version of the spec, for consistency with new DOM APIs, for promise-returning methods to accept an AbortSignal. We could then deprecate .abort() over time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Payment Request API's promise-returning methods and the existing .abort() behavior, then compare how AbortSignal is used by related DOM APIs. Done means the specification defines AbortSignal acceptance and a clear deprecation path for .abort(); the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100