Revision eb9f8a917a751b5bd2e4ed86840eac8b5c4445f2 authored by Brian Birtles on 15 March 2018, 06:57:09 UTC, committed by Brian Birtles on 15 March 2018, 06:57:09 UTC
This patch also drops the test that an AnimationEffectTiming object is created in the appropriate realm since it is no longer the case that a separate timing object is created.
1 parent df2153f
timeout-multiple-fetches.html
<!doctype html>
<title>XMLHttpRequest: timeout, redirects, and CORS preflights</title>
<script src=/resources/testharness.js></script>
<script src=/resources/testharnessreport.js></script>
<script src=/common/get-host-info.sub.js></script>
<div id=log></div>
<script>
async_test(t => {
const client = new XMLHttpRequest
client.open("GET", "resources/redirect.py?delay=500&location=delay.py") // 500 + 500 = 1000
client.timeout = 1000
client.send()
client.ontimeout = t.step_func_done(() => {
assert_equals(client.readyState, 4)
})
client.onload = t.unreached_func("load event fired")
}, "Redirects should not reset the timer")
async_test(t => {
const client = new XMLHttpRequest
client.open("YO", get_host_info().HTTP_REMOTE_ORIGIN + "/xhr/resources/delay.py")
client.timeout = 1000
client.send()
client.ontimeout = t.step_func_done(() => {
assert_equals(client.readyState, 4)
})
client.onload = t.unreached_func("load event fired")
}, "CORS preflights should not reset the timer")
</script>
Computing file changes ...
