Closed ZainManji closed 9 years ago
Good call. I will roll a fix for this into the 1.3.7 release, which will be along shortly.
@jeremyckahn I think the inverse bug would appear if you set seek to a value higher than the duration of the tweenable. Maybe also bound the value with a Math.min(millisecond, this.duration)
?
@SBoudrias I was thinking about that, but it's actually a non-issue. The tween just naturally terminates when the seek
millisecond is greater than the duration: http://codepen.io/jeremyckahn/pen/EaxXZK
It's a bit less explicit the way it is now, but I would prefer less code if possible.
If it's not an issue than that seem fair to me. Thanks for being so reactive!
If I enter a seek value less than 0, it should default to the properties specified at 0ms.
For example,