Fix FXiOS-12300 [Tab Optimization] Only persist tab data after tabs have been removed #29911
+42
−8
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.
📜 Tickets
Jira ticket
Github issue
Jira ticket
Github issue
💡 Description
Clean up remove tab logic so we are only doing the necessary tab persistence. Everywhere in the tab manager code we are persisting data more times than we need to. We should not need to re-select the tab and persist tab session data for each tab we remove.
This update:
There is no need to commit changes after this because select tab preserves tabs
With 200 tabs this greatly increases the tab performance.
TabManager.removeAllTabs
Before: 5.15 s 37.7%
After: 41.00 ms 3.4%
🎥 Demos
Demo
📝 Checklist