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
send-redirect-infinite-sync.htm
<!doctype html>
<html>
<head>
<title>XMLHttpRequest: send() - Redirects (infinite loop; sync)</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<link rel="help" href="https://xhr.spec.whatwg.org/#infrastructure-for-the-send()-method" data-tested-assertations="following::dl[1]/dt[2] following::dl[1]/dd[2]/p[1]" />
<link rel="help" href="https://xhr.spec.whatwg.org/#network-error" data-tested-assertations=".." />
<link rel="help" href="https://xhr.spec.whatwg.org/#request-error" data-tested-assertations="following::ol[1]/li[5]" />
</head>
<body>
<div id="log"></div>
<script>
function redirect(code) {
test(function() {
var client = new XMLHttpRequest()
client.open("GET", "resources/infinite-redirects.py?type="+code, false)
assert_throws("NetworkError", function() { client.send(null) })
}, document.title + " (" + code + ")")
}
redirect("301")
</script>
</body>
</html>
Computing file changes ...
