Bug 1141710, part 4 - Avoid race condition when taking timestamps by reusing the original timestamp. r=dholbert
☠☠ backed out by 24872a839d9d ☠ ☠
authorJonathan Watt <jwatt@jwatt.org>
Mon, 02 Mar 2015 20:05:01 +0000
changeset 232909 ac29161a0f983b37088f6e86a9933652089e6e75
parent 232908 ee29275a17480cf47c6b702f5b10144be4c2013c
child 232910 0bf9f153d5bc21cd8ea1f72f845c5171361bde42
push id56680
push userjwatt@jwatt.org
push dateWed, 11 Mar 2015 00:34:08 +0000
treeherdermozilla-inbound@0e360d3f690b [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersdholbert
bugs1141710
milestone39.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1141710, part 4 - Avoid race condition when taking timestamps by reusing the original timestamp. r=dholbert
dom/animation/test/css-animations/test_animation-player-starttime.html
--- a/dom/animation/test/css-animations/test_animation-player-starttime.html
+++ b/dom/animation/test/css-animations/test_animation-player-starttime.html
@@ -301,17 +301,17 @@ test(function(t)
 
   // XXX Ideally we would have a test to check the ready Promise is initially
   // unresolved, but currently there is no Web API to do that. Waiting for the
   // ready Promise with a timeout doesn't work because the resolved callback
   // will be called (async) regardless of whether the Promise was resolved in
   // the past or is resolved in the future.
 
   var currentTime = document.timeline.currentTime;
-  player.startTime = document.timeline.currentTime;
+  player.startTime = currentTime;
   assert_approx_equals(player.startTime, currentTime, 0.0001, // rounding error
     'Check setting of startTime actually works');
 
   checkStateOnSettingStartTimeToAnimationCreationTime(player);
 }, 'Examine newly created Animation');
 
 
 async_test(function(t) {