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.

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

Allow instantaneous tab switching again #7832

Closed
sboukortt opened this issue Oct 5, 2020 · 4 comments
Closed

Allow instantaneous tab switching again #7832

sboukortt opened this issue Oct 5, 2020 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@sboukortt
Copy link

Environment

Windows build number: Microsoft Windows [version 10.0.19041.508]
Windows Terminal version (if applicable): 1.3.2651.0

Steps to reproduce

  1. Bind a shortcut to action “prevTab” or “nextTab”. (In my case, the shortcuts are “shift+left” and “shift+right” respectively.)

  2. With several tabs open, execute the shortcut.

Expected behavior

The tab switches as soon as the key (“left” or “right” for me) is pressed down, as used to be the case from what I remember.

Actual behavior

The tab doesn’t change until the modifier key (e.g. “shift”) of the shortcut is released. Instead, while it is held, a menu like this is presented, and left/right in my example only change the selection in the menu:

tab-switching

Presumably, the change is intentional, so maybe some people like it more, but I really don’t (I can’t quickly glance at the tabs’ contents as I go through them) and I would really like if the old behavior were at least be accessible via a global setting.

Thanks.

@sboukortt sboukortt added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 5, 2020
@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 Oct 5, 2020
@jack775544
Copy link

Set "useTabSwitcher": false in your profile and you will get the old behaviour.

@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #7409 for more discussion.

/dup #7409

@ghost
Copy link

ghost commented Oct 5, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Oct 5, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Oct 5, 2020
@sboukortt
Copy link
Author

Set "useTabSwitcher": false in your profile and you will get the old behaviour.

Oh, I was redirected to the fr-ch version of the documentation on global settings and not the en-us one, and so I didn’t see that option (the translation doesn’t list it). Thanks for pointing it out.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants