Fix case where absolute nodes would sometimes not be cloned #1675
Reference in New Issue
Block a user
No description provided.
Delete Branch "export-D59175629"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary:
There was a bug where some crash would happen if a tree was cloned that had static/absolute parent/child pair inside it. This was because we were no longer calling
cloneChildrenIfNeeded
on the static parent, but would still layout the absolute child. So that child's owner would be stale and have new layout. In React Native this would lead to a failed assert which causes the crash.The fix here is to clone the children of static nodes during
layoutAbsoluteDescendants
so that we guarantee the node is either cloned if it is going to have new layout.Differential Revision: D59175629
The latest updates on your projects. Learn more about Vercel for Git ↗︎
This pull request was exported from Phabricator. Differential Revision: D59175629
This pull request was exported from Phabricator. Differential Revision: D59175629
This pull request has been merged in facebook/yoga@a1e9abb9b3.
Pull request closed