File: load-event-after-location-set-during-write.window.js

package info (click to toggle)
firefox-esr 78.15.0esr-1~deb10u1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 3,301,296 kB
  • sloc: cpp: 5,665,905; javascript: 4,798,386; ansic: 2,878,233; python: 977,004; asm: 270,347; xml: 181,456; java: 111,756; sh: 72,926; makefile: 21,819; perl: 13,380; cs: 4,725; yacc: 4,565; objc: 3,026; pascal: 1,787; lex: 1,720; ada: 1,681; exp: 505; php: 436; lisp: 260; awk: 152; ruby: 103; csh: 80; sed: 53; sql: 45
file content (19 lines) | stat: -rw-r--r-- 792 bytes parent folder | download | duplicates (28) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
 
// Make sure that the load event for an iframe doesn't fire at the
// point when a navigation triggered by document.write() starts in it,
// but rather when that navigation completes.

async_test(t => {
  const frame = document.body.appendChild(document.createElement("iframe"));
  const doc = frame.contentDocument;
  const url = URL.createObjectURL(new Blob(["PASS"], { type: "text/html"}));

  frame.onload = t.step_func_done(() => {
    assert_equals(frame.contentDocument.body.textContent, "PASS",
                  "Why is our load event firing before the new document loaded?");
  });

  doc.open();
  doc.write(`FAIL<script>location = "${url}"</` + "script>");
  doc.close();
}, "Setting location from document.write() call should not trigger load event until that load completes");