Skip to main content

Browse the archive

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 
[web-animations] Update various references to an effect's `timing` member
 
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
Raw File
abort-after-receive.htm 
<!doctype html>
<html>
  <head>
    <title>XMLHttpRequest: abort() after successful receive should not fire "abort" event</title>
    <script src="/resources/testharness.js"></script>
    <script src="/resources/testharnessreport.js"></script>
    <link rel="help" href="https://xhr.spec.whatwg.org/#the-abort()-method" data-tested-assertations="following::ol[1]/li[4] following::ol[1]/li[5]"/>
  </head>
  <body>
    <div id="log"></div>
    <script>
      var test = async_test();

      test.step(function() {
        var client = new XMLHttpRequest();

        client.onreadystatechange = test.step_func(function() {
          if (client.readyState == 4) {
            // abort should not cause the "abort" event to fire

            client.abort();

            assert_equals(client.readyState, 0);

            test.step_timeout(function(){ // use a timeout to catch any implementation that might queue an abort event for later - just in case
              test.done()
            }, 200);
          }
        });

        client.onabort = test.step_func(function () {
            // this should not fire!

            assert_unreached("abort() should not cause the abort event to fire");
        });

        client.open("GET", "resources/well-formed.xml", true);
        client.send(null);
      });
    </script>
  </body>
</html>
back to top