Open NeXTs opened 7 years ago
I got a similar problem, the number "stuck" at the end of animation
This is the screen cap when no missing frame
This is the screen cap when the bug appear
The component's state currentValue
stuck in "50" where currentTime
updating
I got similar problem, some times it's not right, not every times. How to fix it~~~
Let's say we need to animate value from 0 to 2.5 during 600ms. Sometimes on iphone 5se (Chrome) last frame is missed, so value stops on 2.46 (for example) instead of 2.5. Layout will be updated with correct value after some user interaction, for example select text with value.
settings:
I've added shouldComponentUpdate to make sure another updates don't impact this, but this strange behavior still occurs sometimes on mobile.
Have you noticed something like this?