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

package info (click to toggle)
thunderbird 1%3A115.16.0esr-1~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 3,476,252 kB
  • sloc: cpp: 6,972,150; javascript: 5,209,211; ansic: 3,507,222; python: 1,137,609; asm: 432,531; xml: 205,149; java: 175,761; sh: 116,485; makefile: 22,152; perl: 13,971; objc: 12,561; yacc: 4,583; pascal: 2,840; lex: 1,720; ruby: 1,075; exp: 762; sql: 666; awk: 580; php: 436; lisp: 430; sed: 70; csh: 10
file content (19 lines) | stat: -rw-r--r-- 792 bytes parent folder | download | duplicates (29)
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");