-
Notifications
You must be signed in to change notification settings - Fork 16
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
Use [=AbortSignal/abort reason=]
#86
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @saschanaz! Looks (mostly) great.
I think we can merge once WPTs are ready... and how are implementations going? |
5cb2d99
to
4933b62
Compare
Will take a look at Gecko implementation soon-ish. |
Split from w3c#86 as it's not directly related to abort reasons.
The patch has landed to Gecko and WPT changes are here: web-platform-tests/wpt#32055 |
Nice! I suppose we need a tracking bug in Blink... |
Could you open one or should I? |
SHA: 526a0fe Reason: push, by @inexorabletash Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
crbug.com/1279877 |
Updated in the spec a year ago[1], if the AbortSignal has a reason, use that as the rejection, rather than a stock AbortError w/ hardcoded message. The WPTs didn't cover verifying the reason for an already-aborted signal, so add coverage for those cases too. [1] w3c/web-locks#86 Bug: 1279877 Change-Id: I9838805b10dbb3dae0371abe41faf922344a43f3
Updated in the spec a year ago[1], if the AbortSignal has a reason, use that as the rejection, rather than a stock AbortError w/ hardcoded message. The WPTs didn't cover verifying the reason for an already-aborted signal, so add coverage for those cases too. [1] w3c/web-locks#86 Bug: 1279877 Change-Id: I9838805b10dbb3dae0371abe41faf922344a43f3
Updated in the spec a year ago[1], if the AbortSignal has a reason, use that as the rejection, rather than a stock AbortError w/ hardcoded message. The WPTs didn't cover verifying the reason for an already-aborted signal, so add coverage for those cases too. [1] w3c/web-locks#86 Bug: 1279877 Change-Id: I9838805b10dbb3dae0371abe41faf922344a43f3
Updated in the spec a year ago[1], if the AbortSignal has a reason, use that as the rejection, rather than a stock AbortError w/ hardcoded message. The WPTs didn't cover verifying the reason for an already-aborted signal, so add coverage for those cases too. [1] w3c/web-locks#86 Bug: 1279877 Change-Id: I9838805b10dbb3dae0371abe41faf922344a43f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4112925 Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1084556}
Updated in the spec a year ago[1], if the AbortSignal has a reason, use that as the rejection, rather than a stock AbortError w/ hardcoded message. The WPTs didn't cover verifying the reason for an already-aborted signal, so add coverage for those cases too. [1] w3c/web-locks#86 Bug: 1279877 Change-Id: I9838805b10dbb3dae0371abe41faf922344a43f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4112925 Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1084556}
Updated in the spec a year ago[1], if the AbortSignal has a reason, use that as the rejection, rather than a stock AbortError w/ hardcoded message. The WPTs didn't cover verifying the reason for an already-aborted signal, so add coverage for those cases too. [1] w3c/web-locks#86 Bug: 1279877 Change-Id: I9838805b10dbb3dae0371abe41faf922344a43f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4112925 Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1084556}
…nal, use signal's reason, a=testonly Automatic update from web-platform-tests Web Locks: If aborted due to an AbortSignal, use signal's reason Updated in the spec a year ago[1], if the AbortSignal has a reason, use that as the rejection, rather than a stock AbortError w/ hardcoded message. The WPTs didn't cover verifying the reason for an already-aborted signal, so add coverage for those cases too. [1] w3c/web-locks#86 Bug: 1279877 Change-Id: I9838805b10dbb3dae0371abe41faf922344a43f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4112925 Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1084556} -- wpt-commits: 9ce4a6482a088da3d74f895d8ad15c5ce0c25d28 wpt-pr: 37535
…nal, use signal's reason, a=testonly Automatic update from web-platform-tests Web Locks: If aborted due to an AbortSignal, use signal's reason Updated in the spec a year ago[1], if the AbortSignal has a reason, use that as the rejection, rather than a stock AbortError w/ hardcoded message. The WPTs didn't cover verifying the reason for an already-aborted signal, so add coverage for those cases too. [1] w3c/web-locks#86 Bug: 1279877 Change-Id: I9838805b10dbb3dae0371abe41faf922344a43f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4112925 Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1084556} -- wpt-commits: 9ce4a6482a088da3d74f895d8ad15c5ce0c25d28 wpt-pr: 37535
From whatwg/dom#1030
cc @annevk
Will also modify relevant WPT tests soon.
Preview | Diff