Is there any way to navigate the search editor (whole workspace search) using only cursor keys in vscode ? I'm talking about the whole workspace search and not just the find/replace search.This is the editor I'm talking about
- 
 Can you include a picture or some sort of visual descriptor because vscode has multiple search ‘editors’. Either way you should be above to navigate tabbing through the elements, or forcing tab trapping mode code.visualstudio.com/docs/editor/accessibility#_tab-navigationsoulshined– soulshined2020年07月26日 22:30:44 +00:00Commented Jul 26, 2020 at 22:30
- 
 included an image.pandith padaya– pandith padaya2020年07月26日 22:43:58 +00:00Commented Jul 26, 2020 at 22:43
- 
 Please mark my answer accepted if it helped pandith, otherwise let me know where I can improvesoulshined– soulshined2020年07月28日 16:22:50 +00:00Commented Jul 28, 2020 at 16:22
- 
 For reference: Search Editor docs (snap shots) and release notes of v1.43 from February 2020.cachius– cachius2023年03月10日 11:18:53 +00:00Commented Mar 10, 2023 at 11:18
1 Answer 1
The new search editor thankfully has ported over most of the shortcut commands you have grown to know, but for brevity, this answer will include only the default keybinds with respective command id.
The when expression most commonly associated with these keybinds, should you want to alter them, are :
inSearchEditor
hasSearchResult
searchInputBoxFocus
Searching
Context Lines
- Toggle context lines : toggleSearchEditorContextLinesALT + LWill show n lines before or after search result, for context 
- Reduce context line quantity : decreaseSearchEditorContextLinesALT + -
- Increase context line quantity : increaseSearchEditorContextLinesALT + =
Query Details
- Toggle Query Details : workbench.action.search.toggleQueryDetailsThis will toggle the include/exclude file input boxes 
Settings
- Toggle Match Case : toggleSearchCaseSensitiveALT + C
- Toggle Regex : toggleSearchEditorRegexALT + R
- Toggle Word Match : toggleSearchEditorWholeWordALT + W
Navigation
Luckily, because the search editor is effectively an 'editor', you can continue to use all the keybinds that you are used to. So, in order to jump straight to the editor, you can use whatever your keybind is to jump to an editor group, default is: CTRL + 1 (commandId: workbench.action.focusFirstEditorGroup)
Navigating matches
- Go to next match : search.action.focusNextSearchResultF4
- Go to previous match : search.action.focusPreviousSearchResultSHIFT + F4
- Select all matches : selectAllSearchEditorMatchesCTRL + SHIFT + L
Results
- Deleting result block : - workbench.action.searchEditor.deleteResultBlockCTRL + SHIFT + BACKSPACE- This deletes a block of results from the editor - For example, in the picture below, if my cursor is anywhere in the 'convert.js' result block the entire convert.js matches would be removed. You can undo this with CTRL + Z 
- Go To Definition (effectively go to file) - You can peek with ALT + F12 when your cursor is anywhere on the file name
- You can assign a keyboard shortcut to follow links for the commandId: editor.action.openLinkfor when your cursor is on the file name
- You can go directly to the file & line number of the search result using F12 while your cursor is anywhere on that result
 
Navigate Back to Input Box
- Focus Search Input Box From Results: search.action.focusQueryEditorWidgetESCAPE
Searching within Search Editor
As noted, the search editor is effectively an editor, so you can resume using CTRL + F (find) or CTRL + H (find/replace) to narrow down results even more, and the keybinds set for those are maintained as used elsewhere.
Miscellaneous
- Search again: rerunSearchEditorSearchCTRL + SHIFT + RPerhaps you deleted too many result blocks 
Otherwise, while your cursor is actively in the editor (results), you have the freedom to use most of your keybinds per normal, including collapsing/folding, jumping, copying, moving to editor groups etc