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

The new popup on ctrl+tab is horrendous #7737

Closed
TheDirigible opened this issue Sep 25, 2020 · 6 comments
Closed

The new popup on ctrl+tab is horrendous #7737

TheDirigible opened this issue Sep 25, 2020 · 6 comments
Labels
Issue-Question For questions or discussion Needs-Tag-Fix Doesn't match tag requirements Resolution-Answered Related to questions that have been answered

Comments

@TheDirigible
Copy link

I need to see the tab I'm going to highlighted, not a separate window pop up.

@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 Sep 25, 2020
@pmorch
Copy link

pmorch commented Sep 25, 2020

Especially if I have multiple tabs with the same title, it is less useful than what was before.

@zadjii
Copy link

zadjii commented Sep 25, 2020

This isn't really constructive feedback though, is it? Any ideas how it could be improved?

Maybe "When selecting a new tab with the tab switcher, preview the selected tab in the Terminal", #7409?

Maybe you want to disable the tab switcher, with "useTabSwitcher": false?

@TheDirigible
Copy link
Author

TheDirigible commented Sep 25, 2020

Really constructive feedback would be, don't create any UX change without user feedback, and try not to fix what isn't broken. But this being Microsoft, I'll settle for, please give me a way to disable it.

Ahh apparently "useTabSwitcher":false is a real thing. Thanks!

@zadjii
Copy link

zadjii commented Sep 25, 2020

don't create any UX change without user feedback,

You mean feedback like:
"Feature Request: An advanced tab switcher" #1502

@DHowett
Copy link
Member

DHowett commented Sep 25, 2020

Yeah, we created this feature due to overwhelming community feedback in support of it. We also gave folks the option to turn it off due to our community's likewise-overwhelming ability to be curmudgeonly.

@DHowett DHowett closed this as completed Sep 25, 2020
@DHowett DHowett added Issue-Question For questions or discussion Resolution-Answered Related to questions that have been answered and removed Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Sep 25, 2020
@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Sep 25, 2020
@TheDirigible
Copy link
Author

You're mistaking a few people requesting something with a majority, leading you to turn this on by default. Defying the conventional logic of every other terminal in existence should require a more detailed user survey. Programmers should not be making these decisions, that's what UX people are for. This kind of thinking is what leads a company to think a full screen "your files are exactly where you left them" is a good idea. That's not curmudgeonly, that's logic and more than a passing understanding of UX.

The effect of mistakes like this could be lessened by showing release notes when there's an update, like Sublime Text does. Instead, this thing silently updated, closing all my tabs in the process. Same old Microsoft, 40 years of telling the user what they want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Question For questions or discussion Needs-Tag-Fix Doesn't match tag requirements Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

4 participants