mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Joshua Gross
b3865a9143
Summary: Imagine the scenario in which there's an ongoing UPDATE animation; a REMOVE+INSERT (move) is queued up for the same tag, but there's no new corresponding UPDATE - so maybe the indices of the view have changed, but the layout stays the same. Under the old model, the previous animation would be canceled and the node would jump to the final position. In theory, if there's no new UPDATE, we should continue animating the node to its final position. I'm much happier with this - conflicting animations transition into each other super seamlessly now, and I think the logic is more straightforward as well. Changelog: [Internal] Reviewed By: sammy-SC Differential Revision: D25071664 fbshipit-source-id: fcefc4619dc34cdafdc4d8e8e730b935e5528290