Closed Bug 1736302 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 31291 - DOM: add tests for AbortSignal.reason

Categories

(Core :: DOM: Core & HTML, task, P4)

Product:
Core
Component:
DOM: Core & HTML
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
96 Branch
Tracking Flags:
Tracking Status
firefox96 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 31291 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/31291
Details from upstream follow.

Nidhi Jaju <nidhijaju@chromium.org> wrote:

DOM: add tests for AbortSignal.reason

Add tests for AbortSignal's new abort reason property.

See https://github.com/whatwg/dom/pull/1027 for accompanying spec change.

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

Ran 11 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 10 subtests

Status Summary

Firefox

OK : 2
PASS: 8
FAIL: 12

Chrome

OK : 2
PASS: 8
FAIL: 12

Safari

OK : 2
PASS: 8
FAIL: 12

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/dom/abort/event.any.html
AbortController abort() should fire event synchronously: FAIL (Chrome: FAIL, Safari: FAIL)
AbortController abort(reason) should set signal.reason: FAIL (Chrome: FAIL, Safari: FAIL)
aborting AbortController without reason creates an "AbortError" DOMException: FAIL (Chrome: FAIL, Safari: FAIL)
AbortController abort(undefined) creates an "AbortError" DOMException: FAIL (Chrome: FAIL, Safari: FAIL)
static aborting signal should have right properties: FAIL (Chrome: FAIL, Safari: FAIL)
static aborting signal with reason should set signal.reason: FAIL (Chrome: FAIL, Safari: FAIL)
/dom/abort/event.any.worker.html
AbortController abort() should fire event synchronously: FAIL (Chrome: FAIL, Safari: FAIL)
AbortController abort(reason) should set signal.reason: FAIL (Chrome: FAIL, Safari: FAIL)
aborting AbortController without reason creates an "AbortError" DOMException: FAIL (Chrome: FAIL, Safari: FAIL)
AbortController abort(undefined) creates an "AbortError" DOMException: FAIL (Chrome: FAIL, Safari: FAIL)
static aborting signal should have right properties: FAIL (Chrome: FAIL, Safari: FAIL)
static aborting signal with reason should set signal.reason: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ea7f2da127d8
[wpt PR 31291] - DOM: add tests for AbortSignal.reason, a=testonly
https://hg.mozilla.org/integration/autoland/rev/3b6e1319c9cd
[wpt PR 31291] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/ea7f2da127d8
https://hg.mozilla.org/mozilla-central/rev/3b6e1319c9cd

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox96: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
You need to log in before you can comment on or make changes to this bug.