Closed
Description
I somehow forgot that AbortSignal is a pretty popular API these days. There's more than Fetch and Streams to update. For each impacted specification not only do we need to migrate away from the "aborted flag", we also need to make sure they take into account the object's abort reason, in a matter that is appropriate for the API.
- Add abort reason to abort fetch fetch#1343
- WritableStreamDefaultController.abortReason streams#1165 & Use abort reason in ReadableStreamPipeTo streams#1182
- Fix the "aborted flag" reference w3c/webauthn#1682
- Update "aborted flag" references and use "abort reason" instead w3c/web-nfc#630
- Web Bluetooth
- Update for changes to the AbortSignal spec WICG/navigation-api#188
- EyeDropper Update with DOM's abort reason WICG/eyedropper-api#25
- Idle Detection Update with DOM's abort reason WICG/idle-detection#48
- Update for AbortSignal's abort reason WICG/scheduling-apis#53
- Use
[=AbortSignal/abort reason=]w3c/web-locks#86 - Credential Management
- Geolocation Sensor Update with DOM's abort reason w3c/geolocation-sensor#53
- Add AbortSignal's abort reason to WebOTP WICG/web-otp#56