CSS: Skip the px-appending logic for animations of non-element props
[jquery.git] / test / karma.context.html
blobe4f8a4f88541962af7d2c7cb329fffcd4e185d53
1 <!DOCTYPE html>
2 <html lang="en" id="html">
3 <head>
4 <meta charset="utf-8">
5 <title>CONTEXT</title>
6 <!-- Karma serves this page from /context.html. Other files are served from /base -->
7 <link rel="stylesheet" href="/base/test/data/testsuite.css" />
8 </head>
9 <body id="body">
10 <div id="qunit"></div>
12 <!-- Start: jQuery Test HTML -->
13 <!-- this iframe is outside the #qunit-fixture so it won't waste time by constantly reloading; the tests are "safe" and clean up after themselves -->
14 <iframe id="loadediframe" name="loadediframe" style="display:none;" src="/base/test/data/iframe.html"></iframe>
15 <div id="qunit-fixture"></div>
16 <!-- End: jQuery Test HTML -->
18 <!-- Start: Karma boilerplate -->
19 <script src="/context.js"></script>
20 <script>
21 %CLIENT_CONFIG%
22 window.__karma__.setupContext(window);
24 %MAPPINGS%
25 </script>
26 %SCRIPTS%
27 <!-- End: Karma boilerplate -->
29 <script src="/base/test/data/qunit-fixture.js"></script>
30 <script>
31 // Workaround: Remove call to window.__karma__.loaded()
32 // in favour of calling window.__karma__.start() at window.onload
33 // because tests such as unit/ready.js should run after document ready
34 window.addEventListener('load', function() {
35 window.__karma__.start();
37 // Workaround: https://github.com/karma-runner/karma-qunit/issues/92
38 QUnit.testStart(function () {
39 // Restore content
40 document.getElementById("qunit-fixture").innerHTML = QUnit.config.fixture;
41 });
42 });
43 </script>
44 </body>
45 </html>