BugFix: Fix openTabs limiting logic to always keep only the last 10 items #1025
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.



Previously, the logic for limiting
openTabsrelied onreverse() + splice(10, 1000) + reverse().This worked only if the total number of open tabs never exceeded 1010.
If a user accumulated more than 1000 tabs (e.g. 1140 over a year of usage), the result would incorrectly keep 140 tabs instead of just the last 10.
This PR replaces that logic with a simpler and correct approach: