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.

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

Merged
merged 7 commits into from
Dec 14, 2021
Merged

Conversation

saschanaz
Copy link
Member

@saschanaz saschanaz commented Nov 10, 2021

From whatwg/dom#1030

cc @annevk

Will also modify relevant WPT tests soon.


Preview | Diff

index.bs Show resolved Hide resolved
index.bs Show resolved Hide resolved
Copy link
Member

@annevk annevk left a 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.

index.bs Outdated Show resolved Hide resolved
index.bs Show resolved Hide resolved
@inexorabletash
Copy link
Member

I think we can merge once WPTs are ready... and how are implementations going?

@saschanaz
Copy link
Member Author

Will take a look at Gecko implementation soon-ish.

inexorabletash added a commit that referenced this pull request Nov 12, 2021
Factor turning on "Assume Explicit For" out of #75.

Purely editorial, adding "blah/" as needed to satisfy Bikeshed.

Note that "No 'dfn' refs found for 'aborted flag' with for='['AbortSignal']'." is currently reported, will be fixed by #86
saschanaz added a commit to saschanaz/web-locks that referenced this pull request Nov 12, 2021
Split from w3c#86 as it's not directly related to abort reasons.
inexorabletash pushed a commit that referenced this pull request Nov 12, 2021
Split from #86 as it's not directly related to abort reasons.
@saschanaz
Copy link
Member Author

The patch has landed to Gecko and WPT changes are here: web-platform-tests/wpt#32055

@inexorabletash
Copy link
Member

Nice! I suppose we need a tracking bug in Blink...

@saschanaz
Copy link
Member Author

Could you open one or should I?

@inexorabletash inexorabletash merged commit 526a0fe into w3c:main Dec 14, 2021
@saschanaz saschanaz deleted the abort-reason branch December 14, 2021 17:32
github-actions bot added a commit that referenced this pull request Dec 14, 2021
SHA: 526a0fe
Reason: push, by @inexorabletash

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@inexorabletash
Copy link
Member

crbug.com/1279877

chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Dec 15, 2022
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
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Dec 16, 2022
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
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Dec 16, 2022
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
aarongable pushed a commit to chromium/chromium that referenced this pull request Dec 16, 2022
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}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Dec 16, 2022
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}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Dec 16, 2022
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}
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request Dec 22, 2022
…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
jamienicol pushed a commit to jamienicol/gecko that referenced this pull request Jan 3, 2023
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants