fix/global bounds - #152
Merged
Merged
Conversation
✅ Deploy Preview for rnst-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
2 participants
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.
Motivation
Bounds handoffs could become unreliable when transitions crossed nested navigation boundaries or when the active transition pair changed before a closing animation settled. This could cause shared content to disappear, jump between hosts, or lose its destination during rapid or overlapping navigation.
This PR stabilizes that lifecycle by coordinating bounds globally, retaining active handoffs until their actual transition completes, and ensuring root boundaries render through the correct handoff host even without an explicit
Boundary.Target.The goal is to make existing bounds transitions reliable across nested stacks and repeated navigation flows. It introduces no new public API or product feature; it is a final v3 stability fix. It also raises the minimum supported
react-native-teleportversion to1.2.0, which provides the public portal behavior required by the corrected implementation.