-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Open
Labels
MonthlyKSv2KSv2
Description
TransitionTracker Direct Usage
Refer to README.md for more information what's the overall strategy and why we're migrating away from InteractionManager.runAfterInteractions.
Strategy
**Use TransitionTracker.runAfterTransitions **
These are utility files where TransitionTracker.runAfterTransitions should be called directly. This is the exception to the general rule — application code should use Navigation.afterTransition or KeyboardUtils.dismiss({afterTransition}) instead, but these utility files need the direct API.
Usages
| File | Line | Current | Migration | PR |
|---|---|---|---|---|
Performance.tsx |
49 | InteractionManager wrapping TTI measurement | Use TransitionTracker.runAfterTransitions |
#54412 |
Lottie/index.tsx |
44 | InteractionManager gating Lottie rendering | Use TransitionTracker.runAfterTransitions |
#48143 |
BackgroundImage/index.native.tsx |
38 | InteractionManager deferring background load | Use TransitionTracker.runAfterTransitions |
#48143 |
BackgroundImage/index.tsx |
38 | InteractionManager deferring background load | Use TransitionTracker.runAfterTransitions |
#48143 |
TopLevelNavigationTabBar/index.tsx |
54 | InteractionManager detecting animation finish | Use TransitionTracker.runAfterTransitions |
#49539 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
MonthlyKSv2KSv2
Type
Projects
Status
No status