Closed Bug 1743818 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 31810 - [FedCM] Add wpt test for concurrent navigator.credentials.get

Categories

(Core :: DOM: Security, task, P4)

task

Tracking

()

RESOLVED FIXED
97 Branch
Tracking Status
firefox97 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream][domsecurity-backlog])

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

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

Yi Gu <yigu@chromium.org> wrote:

[FedCM] Add wpt test for concurrent navigator.credentials.get

When there's a pending request for id token, all new requests by get
will be rejected. This patch adds a wpt test for it.

Bug: 1274805
Change-Id: I024abc5b2ff90c04d5c4d205b036a509d20943a0
Reviewed-on: https://chromium-review.googlesource.com/3309110
WPT-Export-Revision: 88c13190894241a28a902a6970ecee3e88ab39bf

Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Whiteboard: [wptsync downstream][domsecurity-backlog] → [wptsync downstream]

CI Results

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

Total 2 tests

Status Summary

Firefox

TIMEOUT: 2

Chrome

TIMEOUT: 2

Safari

TIMEOUT: 2

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/credential-management/fedcm-revoke.https.html: TIMEOUT (Chrome: TIMEOUT, Safari: TIMEOUT)
/credential-management/fedcm.https.html: TIMEOUT (Chrome: TIMEOUT, Safari: TIMEOUT)

Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ad0f475b303c
[wpt PR 31810] - [FedCM] Add wpt test for concurrent navigator.credentials.get, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
You need to log in before you can comment on or make changes to this bug.