This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20113 - incorrect algorithm when setting TimedItem::locallyPaused
Summary: incorrect algorithm when setting TimedItem::locallyPaused
Status: RESOLVED FIXED
Alias: None
Product: FXTF
Classification: Unclassified
Component: Web Animations (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: FXTF Web Animation bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-28 02:45 UTC by Shane Stephens
Modified: 2013-12-19 07:35 UTC (History)
1 user (show)

See Also:

Attachments

Description Shane Stephens 2012-11-28 02:45:00 UTC 
the locallyPaused property of TimedItem includes the following text:


3. The next step depends on the current value of locallyPaused as follows,
If locallyPaused is true,
Record the current value of currentTime as pause start time.
If locallyPaused is false,
Set the stored value of timeDrift to the result of evaluating effective parent time - startTime - pause start time.

The comparison values here for locallyPaused are backwards (i.e. if locallyPaused is false then pause start time should be set to the current value of currentTime).
Comment 1 Brian Birtles 2013-12-19 07:35:03 UTC 
Although I haven't traced down the exact changeset where this was fixed, I confirmed that it has been fixed in the latest ED.