fix: Fall back to layout position when item position is unset#555
Open
MatiPl01 wants to merge 2 commits into
Open
fix: Fall back to layout position when item position is unset#555MatiPl01 wants to merge 2 commits into
MatiPl01 wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes grid/flex items not appearing until the first scroll on Reanimated 4.4 (#552).
When absolute layout becomes active, an item's animated
positionmay not be propagated yet, so it would render withHIDDEN_STYLEand stay hidden until a scroll re-ran the layout. This falls back to the item'slayoutPosition(fromitemPositions) whilepositionis stillnull, so items render at their correct slots immediately.positionstays primary (drag/reorder animations unaffected), andHIDDEN_STYLEis kept only as the both-nullfallback.Closes #552