File: sync-no-timeout.any.js

package info (click to toggle)
firefox-esr 115.15.0esr-1~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 3,659,216 kB
  • sloc: cpp: 6,676,686; javascript: 5,690,965; ansic: 3,328,546; python: 1,120,594; asm: 397,163; xml: 180,531; java: 178,838; sh: 68,930; makefile: 20,999; perl: 12,595; objc: 12,561; yacc: 4,583; cs: 3,846; pascal: 2,840; lex: 1,720; ruby: 1,079; exp: 762; php: 436; lisp: 258; awk: 247; sql: 66; sed: 54; csh: 10
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');