[wpt-sync] Sync PR 48888 - Fenced frame: refactor navigate ancestor tests for headless mode.
Categories
(Core :: DOM: Core & HTML, task, P4)
Tracking
()
People
(Reporter: wpt-sync, Unassigned)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 48888 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/48888
Details from upstream follow.
Liam Brady <lbrady@google.com> wrote:
Fenced frame: refactor navigate ancestor tests for headless mode.
User activation does not work in headless mode when dealing with new
windows. This CL refactors our navigate ancestor tests to run the test
in the main window. This means that the failure condition will now be
different. Rather than an assert being hit, if the test fails, it will
now time out, as the top-level page will have been navigated away.This also simplifies the setup to use remote context executors instead
of a series of various helper files. If this causes flakes down the
line, this will be reverted.Change-Id: I492bd524ad755c8e310264804650ff213a027d80
Bug: 366257368
Reviewed-on: https://chromium-review.googlesource.com/5974698
WPT-Export-Revision: 4701303342517f5c4f71a1c0f58446e999e989c2
Assignee | ||
Updated•3 days ago
|
Assignee | ||
Updated•3 days ago
|
Assignee | ||
Updated•3 days ago
|
Assignee | ||
Comment 1•3 days ago
|
||
Assignee | ||
Comment 2•3 days ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 3 tests and 2 subtests
Status Summary
Firefox
OK
: 3
FAIL
: 6
Chrome
OK
: 3
FAIL
: 6
Safari
OK
: 3
FAIL
: 6
Links
Details
New Tests That Don't Pass
- /fenced-frame/navigate-ancestor-nested-fenced-frame.https.html [wpt.fyi]
- Nested fenced frames that navigate _parent end up navigating themselves:
FAIL
(Chrome:FAIL
, Safari:FAIL
) - Nested fenced frames that navigate _top end up navigating themselves:
FAIL
(Chrome:FAIL
, Safari:FAIL
)
- Nested fenced frames that navigate _parent end up navigating themselves:
- /fenced-frame/navigate-ancestor-nested-iframe.https.html [wpt.fyi]
- Iframes nested in fenced frames fail to navigate _parent:
FAIL
(Chrome:FAIL
, Safari:FAIL
) - Iframes nested in fenced frames fail to navigate _top:
FAIL
(Chrome:FAIL
, Safari:FAIL
)
- Iframes nested in fenced frames fail to navigate _parent:
- /fenced-frame/navigate-ancestor-top-level-fenced-frame.https.html [wpt.fyi]
- Top-level fenced frames that navigate _parent end up navigating themselves:
FAIL
(Chrome:FAIL
, Safari:FAIL
) - Top-level fenced frames that navigate _top end up navigating themselves:
FAIL
(Chrome:FAIL
, Safari:FAIL
)
- Top-level fenced frames that navigate _parent end up navigating themselves:
Description
•