-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added timing constructor test #220
base: master
Are you sure you want to change the base?
Conversation
assert.equal(player.currentTime, 0); | ||
tick(300); | ||
assert.equal(player.startTime, 300); // why does this pass? the anim is running? | ||
assert.equal(player.currentTime, 300, 'after 300ms tick, currentTime should be 300ms'); // this fails -- what, what? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The animation was pending until 300, I'd expect that it's currentTime is actually 0 in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After all, it's start time is 300 per line 19.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've fixed this behaviour with feedback on how tick works. The test is still broken though :)
Conflicts: test/js/animation-constructor.js
assert.equal(player.currentTime, 300); | ||
|
||
timing.iterations = 0.5; | ||
animation.timing.iterations = 0.5; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI these don't work because we don't yet support these maxifill feature (exposed timing, modifiable timing). They're not on the roadmap for the m39 release.
Conflicts: test/js/timing.js
Some failing tests around timing.