Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Set correct initial value for AnimatedComponent for styles backed by …
…native animated nodes Summary: In AnimatedComponent.render, we get the initial values of any styles backed by AnimatedNode, but ONLY for non-native animations. Thus, if convert an animated node to native before the call to render to mount the component, we will end up not applying the initial value until after the component is mounted. This may result in a visible flicker as the expected value is applied some time after the component is mounted and visible. - Without native driver: BaseViewManager.setTransform called during view preallocation (ViewManager.createViewInstance) - With native driver: BaseViewManager.setTransform called during MountingManager.updateProps (called from PropsAnimatedNode.updateView) This diff removes the isNative check in AnimatedStyle and AnimatedProps when traversing style props. This shouldn't be a problem: - Created as non-native, animated with JS driver - This diff does not affect this scenario - Created as non-native, animated with native driver - Initial value is applied correctly on render/mount. On subsequent renders, the outdated value from JS side will not apply on the platform view as it has not changed. - Created as native, animated with native driver - Initial value is applied correctly on render/mount. On subsequent renders, the outdated value from JS side will not apply on the platform view as it has not changed. Changelog: [Internal][Fixed] - Set correct initial value for AnimatedComponent for styles backed by native animated nodes Reviewed By: JoshuaGross, javache Differential Revision: D36612758 fbshipit-source-id: 922d6534c605b3eb0a1d9476753111b726f138f2
- Loading branch information