You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-11-25] [$175] perf: move tab-root gesture logic out of TabNavigator to stop re-renders on navigation #106875
TabNavigator subscribes to the focused route to turn the parent stack's swipe-back gesture off on tab root screens (Home, Inbox, Search, Insights, Settings). Each navigation changes the focused route, so the whole tab navigator re-renders on every navigation, for example when the Search Router opens. On web, TabNavigator re-rendered 15 times over the tested navigation flow, at about 17 ms each in a dev build.
Solution
Move the gesture logic out of TabNavigator (web) and useNativeTabNavigator (native) into a new TabRootGestureController component that renders nothing and sits next to Tab.Navigator. The controller subscribes only to whether the focused route is a tab root, and calls parentNavigation.setOptions({gestureEnabled}) when that value changes. Navigation now re-renders only this empty component, and the tested flow has no TabNavigator re-renders.
changed the title [-]perf: move tab-root gesture logic out of TabNavigator to stop re-renders on navigation[/-][+][$175] perf: move tab-root gesture logic out of TabNavigator to stop re-renders on navigation[/+]on Nov 13, 2026
changed the title [-][$175] perf: move tab-root gesture logic out of TabNavigator to stop re-renders on navigation[/-][+][Due for payment 2026-11-25] [$175] perf: move tab-root gesture logic out of TabNavigator to stop re-renders on navigation[/+]on Nov 18, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.41-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-11-25. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
melvin-bot commentedon Nov 13, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hoangzinh (
External)[-]perf: move tab-root gesture logic out of TabNavigator to stop re-renders on navigation[/-][+][$175] perf: move tab-root gesture logic out of TabNavigator to stop re-renders on navigation[/+]melvin-bot commentedon Nov 13, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022121283463860645108
[-][$175] perf: move tab-root gesture logic out of TabNavigator to stop re-renders on navigation[/-][+][Due for payment 2026-11-25] [$175] perf: move tab-root gesture logic out of TabNavigator to stop re-renders on navigation[/+]melvin-bot commentedon Nov 18, 2026
@hoangzinh
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.41-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-11-25. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
hoangzinh commentedon Nov 19, 2026
No Checklist Needed
Refactoring issue