Forget oldest tab history entry, instead of newest - #155
Open
AjaxGb wants to merge 2 commits into
Open
Conversation
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
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.
Currently, when the tab history hits 50 entries, new entries stop being added entirely. This means that if you open more than 50 tabs and then close one, focus jumps to whatever arbitrary tab was the 50th. Since loading the most recent history entry happens when any tab is closed, not just the active one, the tab you close doesn't even have to be the one that's open. This continues to happen until the history has been reduced to under 50 entries, making navigation very annoying.
Improvements in this PR: