File: sync-no-timeout.any.js

package info (click to toggle)
firefox-esr 91.13.0esr-1~deb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 3,375,652 kB
  • sloc: cpp: 5,762,054; javascript: 5,481,714; ansic: 3,121,191; python: 851,492; asm: 331,172; xml: 178,949; java: 155,554; sh: 63,704; makefile: 20,127; perl: 12,825; yacc: 4,583; cs: 3,846; objc: 3,026; lex: 1,720; exp: 762; pascal: 635; php: 436; lisp: 260; awk: 231; ruby: 103; sed: 53; sql: 46; csh: 45
file content (16 lines) | stat: -rw-r--r-- 613 bytes parent folder | download | duplicates (27) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
 
// META: global=window,dedicatedworker,sharedworker
// META: timeout=long

// This is a regression test for https://crbug.com/844268, when a timeout of 10
// seconds was applied to XHR in Chrome. There should be no timeout unless the
// "timeout" parameter is set on the object.
test(t => {
  let xhr = new XMLHttpRequest();

  // For practical reasons, we can't wait forever. 12 seconds is long enough to
  // reliably reproduce the bug in Chrome.
  xhr.open('GET', 'resources/trickle.py?ms=1000&count=12', false);

  // The test will fail if this throws.
  xhr.send();
}, 'Sync XHR should not have a timeout');