segmentwillchange event fired incorrectly ? about ftscroller HOT 2 OPEN

You're right - when an animation is scheduled via feeding the browser a lengthy CSS3 animation and a bezier curve, we're currently not firing the end until cleanup happens at the end.

There's no perfect solution to this, but what we can do is work out if segments will be crossed by a new animation, and schedule setTimeouts to fire at the appropriate points; it may not be perfect, but it'll be relatively accurate - especially in the case of slow animations, where the missing events are probably most obvious at the moment.

from ftscroller.

Would greatly appreciate a fix to this issue as well.

from ftscroller.