Continuing the discussion from Keyboard shortcuts wish list:
The search box can be activated with / and the autocomplete is really nice. I wish there was a way to navigate through the autocomplete results, e.g. with the up/down arrows.
In the discussion about keyboard shortcuts for autocomplete search results, dandv expressed a desire to navigate through autocomplete results using up/down arrows. cpradio suggested using the Tab key instead, explaining that up/down arrows were replaced with Tab for better accessibility. dandv clarified that they are not suggesting removing Tab support, but rather adding up/down arrow shortcuts, similar to other autocomplete UXes. cpradio argued that having both Tab and up/down arrow shortcuts did not work well in the past, and removing up/down arrows was a better solution. They also highlighted potential tradeoffs, including losing access to certain search features.
Continuing the discussion from Keyboard shortcuts wish list:
The search box can be activated with / and the autocomplete is really nice. I wish there was a way to navigate through the autocomplete results, e.g. with the up/down arrows.
Use Tab. They are links. I think this is a duplicate (as I know it was mentioned elsewhere too)
Up/Down was replaced with tab to provide better accessibility, as without tab support you couldn’t access the “Search this Topic/Category/User” checkbox, the help, or Show More. You also couldn’t get to a user who was returned as a search result.
I know, Tab is a browser-level shortcut that will also go through the “help” link, which defeats the purpose of shortcuts ![]()
I’m not suggesting disabling Tab support.
But up/down right now do exactly what Home/End do. Far from useful.
I updated my post, no, that doesn’t defeat the purpose of shortcuts, it ensures it is accessible, which is super important for keyboard users. You can’t utilize most of the results without using Tab.
Again, I’m not suggesting removing Tab, but adding up/down arrow shortcuts to go through the autocompletion suggestions, as the vast majority of autocomplete UXes behave (Google search, Bootstrap typeahead, Select2 etc.)
You can’t have both. We tried that and it didn’t work well. It uses mousetrap for keyboard shortcuts, so if you can get both to work properly, go for it. I gave it a shot months ago, and removing up/down was the better solution.
Just keep in mind, when you do that, you’ll likely lose the ability to access show more (without also making it access the help text, you can skip it initially, but when you go back up, it would likely select it, but you’d skip the checkbox too). So consider the tradeoffs as you get far less control of your search.