Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature Request - Most Recently Used (MRU) Tabs #2350

Closed
strickdd opened this issue Aug 8, 2019 · 1 comment
Closed

Feature Request - Most Recently Used (MRU) Tabs #2350

strickdd opened this issue Aug 8, 2019 · 1 comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@strickdd
Copy link

strickdd commented Aug 8, 2019

Description of the new feature/enhancement

It would be nice to have the ctrl + tab and ctrl + shift + tab to cycle through most recently used (MRU) order. This option is available in almost all tabbed based products (except Chrome :( ). At the very least it is an option that can be enabled if not already the default behavior.

If I have three tabs open and focus tab 2 then tab 0, pressing ctrl + tab should take me to tab 2. Pressing it again should take me back to tab 0. Holding ctrl and pressing tab twice should focus tab 1. (This is all assuming zero-based indexing of tabs as documented in the profiles.json file) Using the ctrl + shift + tab should focus the last (oldest) focused tab currently open.

Proposed technical implementation details (optional)

I would imagine a circularly linked list may be appropriate.
@strickdd strickdd added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 8, 2019
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Aug 8, 2019
@zadjii-msft
Copy link
Member

This is a dupe of #973

@zadjii-msft zadjii-msft added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Aug 8, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@strickdd @zadjii-msft