Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Origin-keyed agent clusters: make COI imply origin-keying #27193

Merged
merged 1 commit into from Jan 15, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
@@ -0,0 +1,28 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>window.originAgentCluster must be implied by cross-origin isolation</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>

<iframe src="//{{domains[www1]}}:{{location[port]}}/html/browsers/origin/origin-keyed-agent-clusters/resources/coep-frame.html"></iframe>

<div id="log"></div>

<script type="module">
import { testGetter } from "../resources/helpers.mjs";

setup({ explicit_done: true });

window.onload = () => {
// Cross-origin isolated pages are always origin-keyed.
testGetter(self, true, "self");

// Child frames of cross-origin isolated pages must also be cross-origin
// isolated, and thus also origin-keyed. Make sure the implementation doesn't
// treat them specially in some wierd way, for the purposes of this
// implication.
testGetter(0, true, "child");

done();
};
</script>
@@ -0,0 +1,2 @@
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
@@ -0,0 +1,5 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>A page with COEP set that will respond when asked</title>

<script type="module" src="send-header-page-script.mjs"></script>
@@ -0,0 +1,2 @@
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Resource-Policy: cross-origin