Support customization of navigation shortcuts in various views (command palette, code actions popup, ...)

[EdwinVanRooij]

I'd love to use tab more often, instead of moving away from the home row to reach for the arrow keys while programming.
For example: in the command palette, I can navigate through these files by pressing the up- and down arrow keys:

However, I'd much rather navigate here by using Tab for navigating down, and shift+tab for navigating up. I realize that there is a way to add a custom keybinding to this command:

Which works, but only after pressing tab twice each time, because the first time will just select the gear icon in this case:

Or in file navigation, it will select the button that's there:

I've looked at adding '!listFocus' to the command 'tab', hoping it would disable standard 'tab' functionality in this list, but without any luck.

Also, it'd be great if I could use tab to navigate through these kind of options as well:

Does anyone know if the things I'd like to achieve are possible at the moment in any way? Or else, is it something that we can implement?

[EdwinVanRooij]

Regarding the "select next quick fix" (last screenshot) hotkey; it seems like it used to exist, but doesn't anymore. The commands were selectNextQuickFix and selectPrevQuickFix (source: https://blog.lanzani.nl/2016/tab-in-vscode/). Seems weird to me.

[vscodenpa]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vscodenpa]

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[TylerLeonhardt]

You are able to do this now:

        {
		"key": "tab",
		"command": "quickInput.next",
		"when": "inQuickInput && quickInputType == 'quickPick'"
	},

Do keep in mind, you may want to also add the alternatives of quickInput.next with the modifiers to handle Quick Access scenarios (like when you have Ctrl held down)...

Shift+Tab doesn't quite work yet as there is a hardcoded keybinding for that that needs to be sorted.