Bug 1141710, part 4 - Avoid race condition when taking timestamps by reusing the original timestamp. r=dholbert
authorJonathan Watt <jwatt@jwatt.org>
Wed, 04 Mar 2015 02:49:43 +0000
changeset 232938 b7c05cadcbe65bafa931a0cd86d73d0a154559b4
parent 232937 3427f7cbfc35d7b34884090755ea33ee4721771b
child 232939 3fa39b8796078a3b181ed92daa75ac5712b2340e
push id56694
push userjwatt@jwatt.org
push dateWed, 11 Mar 2015 03:04:44 +0000
treeherdermozilla-inbound@d5c21f24c2c8 [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) {