Files
sousa-gecko/testing/web-platform/tests/fenced-frame/unfenced-top-navigation-default.https.html
T
Andrew Verge ed6cdb9369 Bug 1934614 [wpt PR 49468] - Allow _unfencedTop navigation in all fenced frames., a=testonly
Automatic update from web-platform-tests
Allow _unfencedTop navigation in all fenced frames.

Previously, only "opaque ads" fenced frames could navigate the _unfencedTop target, but we should allow all fenced frames to
do so.

While writing the spec for `_unfencedTop`, we re-discovered this limitation, and it was unclear why it existed in the first place. I wrote the spec change to allow the new keyword in all fenced frame types, and this change updates the Chromium implementation to match.

Bug: 380896847
Change-Id: Id02563a3e217042f9c8ac136929f168a7c899d51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6017449
Reviewed-by: Liam Brady <lbrady@google.com>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Commit-Queue: Andrew Verge <averge@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1390314}

--

wpt-commits: 6571a7b9b0064b1c2e9766fc978524eaee74cc2d
wpt-pr: 49468
2024-12-03 11:21:15 +00:00

37 lines
1.2 KiB
HTML

<!DOCTYPE html>
<title>Test '_unfencedTop' navigation from a default-mode fenced frame</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="/common/utils.js"></script>
<script src="/common/dispatcher/dispatcher.js"></script>
<script src="resources/utils.js"></script>
<script src="/resources/testdriver.js"></script>
<script src="/resources/testdriver-actions.js"></script>
<script src="/resources/testdriver-vendor.js"></script>
<script src="/common/get-host-info.sub.js"></script>
<body>
<script>
// This is not our actual test file; instead, this file performs an
// unfenced top navigation to resources/unfenced-top-target.html, which
// contains the actual promise_test. The test should automatically pass if the
// navigation succeeds. See ./automatic-beacon-unfenced-top.https.html for
// another example of this pattern.
async function init() {
let fencedframe = await attachFencedFrameContext();
await fencedframe.execute(() => {
window.onclick = () => {
let opened_url = new URL('unfenced-top-target.html', location.href);
window.open(opened_url, '_unfencedTop');
}
});
await multiClick(10, 10, fencedframe.element);
};
init();
</script>
</body>