ac19276534
Summary: `NavigationCardStackPanResponder` uses `__getValue` and the `stopAnimation` callback value which both doesn't work with native driven animation. The workaround here is to add a value listener so the JS value of the AnimatedValue gets updated too so `__getValue` has a relatively up to date value. This value should be good unless JS lags behind native a lot but that should not happen during a navigation gesture. Also added a comment that explains the hack. **Test plan** Tested in an app that uses native driven animations with a back gesture. This also needs #10643 and #10641 for everything to work properly. Closes https://github.com/facebook/react-native/pull/10642 Differential Revision: D4135496 Pulled By: ericvicenti fbshipit-source-id: 395aff78b16a37ad9407207a05504fdd6311f733 |
||
|---|---|---|
| .. | ||
| assets | ||
| NavigationAnimatedValueSubscription.js | ||
| NavigationCard.js | ||
| NavigationCardStack.js | ||
| NavigationCardStackPanResponder.js | ||
| NavigationCardStackStyleInterpolator.js | ||
| NavigationHeader.js | ||
| NavigationHeaderBackButton.js | ||
| NavigationHeaderStyleInterpolator.js | ||
| NavigationHeaderTitle.js | ||
| NavigationPagerPanResponder.js | ||
| NavigationPagerStyleInterpolator.js | ||
| NavigationPointerEventsContainer.js | ||