Adding upstream version 5.28.2+dfsg1+~cs23.11.12.3.upstream/5.28.2+dfsg1+_cs23.11.12.3upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 16 insertions, 0 deletions

diff --git a/test/wpt/tests/xhr/sync-no-timeout.any.js b/test/wpt/tests/xhr/sync-no-timeout.any.js
new file mode 100644
index 0000000..ac73e0b
--- /dev/null
+++ b/test/wpt/tests/xhr/sync-no-timeout.any.js
@@ -0,0 +1,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');