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
event-readystatechange-loaded.htm
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>XMLHttpRequest: the LOADING state change may be emitted multiple times</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<link rel="help" href="https://xhr.spec.whatwg.org/#the-send()-method" data-tested-assertations="following::ol[1]/li[10]/dt[1]">
</head>
<div id="log"></div>
<script>
var test = async_test();
test.step(function() {
var client = new XMLHttpRequest();
var countedLoading = 0;
client.onreadystatechange = test.step_func(function() {
if (client.readyState === 3) {
countedLoading += 1;
}
if (client.readyState === 4) {
assert_greater_than(countedLoading, 1, "LOADING state change may be emitted multiple times");
test.done();
}
});
client.open("GET", "resources/trickle.py?count=10"); // default timeout in trickle.py is 1/2 sec, so this request will take 5 seconds to complete
client.send(null);
});
</script>
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...