[wpt-sync] Sync PR 45504 - Add explicit waits in notify-event-iframe.https.html
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox126 fixed)
| Tracking | Status | |
|---|---|---|
| firefox126 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 45504 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/45504
Details from upstream follow.
Andrew Verge <averge@chromium.org> wrote:
Add explicit waits in notify-event-iframe.https.html
Previously this test did not wait for postMessages to resolve
before attempting to look at the variable that was messaged into.
Now the variable is a promise, which we explicitly await before
attempting to read the message. This should hopefully help with
flakes.Bug: 331799346
Change-Id: Ic5b00bb4291b568a917d30414603fcdd1513b82c
Reviewed-on: https://chromium-review.googlesource.com/5421229
WPT-Export-Revision: 00e538cc207596fba99f9a471eef9df4293e9143
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 3 subtests
Status Summary
Firefox
OK : 1
FAIL : 3
Chrome
FAIL : 2
TIMEOUT: 2
Safari
OK : 1
FAIL : 3
Links
Details
New Tests That Don't Pass
- /fenced-frame/notify-event-iframe.https.html [wpt.fyi]
- Test that fenced frame notifyEvent() fails in a nested same-origin iframe.:
FAIL(Chrome:FAIL, Safari:FAIL) - Test that fenced frame notifyEvent() fails in a nested cross-origin iframe.:
FAIL(Chrome:FAIL, Safari:FAIL) - Test that notifyEvent() fails in a URN iframe.:
FAIL(Chrome:TIMEOUT, Safari:FAIL)
- Test that fenced frame notifyEvent() fails in a nested same-origin iframe.:
| Assignee | ||
Updated•1 year ago
|
Comment 3•1 year ago
|
||
| bugherder | ||
Description
•