File: config-cross-origin-iframe.https.html

package info (click to toggle)
firefox 149.0-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,767,760 kB
  • sloc: cpp: 7,416,064; javascript: 6,752,859; ansic: 3,774,850; python: 1,250,473; xml: 641,578; asm: 439,191; java: 186,617; sh: 56,634; makefile: 18,856; objc: 13,092; perl: 12,763; pascal: 5,960; yacc: 4,583; cs: 3,846; lex: 1,720; ruby: 1,002; php: 436; lisp: 258; awk: 105; sql: 66; sed: 53; csh: 10; exp: 6
file content (30 lines) | stat: -rw-r--r-- 929 bytes parent folder | download | duplicates (14) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
 
<!DOCTYPE html>
<script src="utils.js"></script>
<script src="/common/get-host-info.sub.js"></script>
<title>Fenced frame attribution reporting self navigation test</title>

<body>
<script>
// This helper function will navigate a child iframe to a remote origin page.
// It will then check to make sure that window.fence APIs are not allowed after
// the navigation. This code is meant to run in a fenced frame.
const [key] = parseKeylist();

const event = {
  eventType: "reserved.top_navigation_commit",
  eventData: "data!",
  destination: ["buyer"],
}

// These should gracefully fail without badmessaging the renderer.
window.fence.setReportEventDataForAutomaticBeacons(event);
window.fence.reportEvent(event);

const configs = window.fence.getNestedConfigs();

// Report how many configs were obtained. Cross-origin pages should not
// obtain any nested configs.
writeValueToServer(key, configs.length);

</script>
</body>