File: subframe-loading.https.html

package info (click to toggle)
firefox 143.0.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,617,328 kB
  • sloc: cpp: 7,478,492; javascript: 6,417,157; ansic: 3,720,058; python: 1,396,372; xml: 627,523; asm: 438,677; java: 186,156; sh: 63,477; makefile: 19,171; objc: 13,059; perl: 12,983; yacc: 4,583; cs: 3,846; pascal: 3,405; lex: 1,720; ruby: 1,003; exp: 762; php: 436; lisp: 258; awk: 247; sql: 66; sed: 53; csh: 10
file content (30 lines) | stat: -rw-r--r-- 983 bytes parent folder | download | duplicates (18) 
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>
<title>Test Subframe Loading Disabler</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>

<body>
<script>

promise_test(async () => {
  const container = document.body.appendChild(document.createElement("div"));

  // Create a helper iframe that triggers loading the new fenced frame
  // simultaneously when the parent container is removed.
  const helperFrame = container.appendChild(document.createElement("iframe"));

  helperFrame.contentWindow.onunload = function() {
    const fenced_frame = document.createElement("fencedframe");
    fenced_frame.src = "resources/dummy.https.html";
    container.appendChild(fenced_frame);
  };

  // If the fenced frame loads when it's not supposed to,
  // a DCHECK will catch that and cause the test to crash.
  document.body.removeChild(container);

}, "Fenced frames should not load if its parent has subframe loading disabled");

</script>
</body>
</html>