Bug 1430841 Re-enable the Reduce Timer Precision pref for CSS Animations tests r?birtles
Currently CSS Animations are exempted from Reduce Timer Precision, so this isn't needed.
Additionally, when we test by overriding that restriction, these tests aren't run, which
leads to confusion.
MozReview-Commit-ID: Gv6T3oGO475
--- a/dom/animation/test/css-animations/test_animation-starttime.html
+++ b/dom/animation/test/css-animations/test_animation-starttime.html
@@ -2,16 +2,14 @@
<meta charset=utf-8>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<div id="log"></div>
<script>
'use strict';
setup({explicit_done: true});
SpecialPowers.pushPrefEnv(
- { "set":
- [["dom.animations-api.core.enabled", true],
- ["privacy.reduceTimerPrecision", false]]},
+ { "set": [["dom.animations-api.core.enabled", true]] },
function() {
window.open("file_animation-starttime.html");
});
</script>
</html>--- a/dom/animation/test/css-animations/test_event-dispatch.html
+++ b/dom/animation/test/css-animations/test_event-dispatch.html
@@ -2,16 +2,14 @@
<meta charset=utf-8>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<div id="log"></div>
<script>
'use strict';
setup({explicit_done: true});
SpecialPowers.pushPrefEnv(
- { "set":
- [["dom.animations-api.core.enabled", true],
- ["privacy.reduceTimerPrecision", false]]},
+ { "set": [["dom.animations-api.core.enabled", true]] },
function() {
window.open("file_event-dispatch.html");
});
</script>
</html>