'Next Result' in document should be higher priority than 'Next Result' in search panel

[jamesford42]

Type: Bug

F3 is "next result" when searching within a document (ctrl+f) but when iterating search results within the search panel it is by default something else that I never remember, so I rebound it to also be F3.

It turns out that if I do this, the search panel results always take priority over the document search result, even if the document has focus, even if the search panel is not open (it just has to have search results from some time ago).

Visual studio manages to use the same key for "next result" for both of these cases, and also seems to go to the appropriate "next" one I meant to, when I press the key. So, work out the rules. But, I surely don't want to have two different keys for them.

VS Code version: Code 1.97.2 (e54c774, 2025-02-12T23:20:35.343Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 x 3600)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	31.91GB (18.31GB free)
Process Argv	--folder-uri file:///d%3A/Projects/Ai_War_2/arcengames_aiw-ultra_git --crash-reporter-id 7b768061-3142-43ef-bd56-5ae000f7d032
Screen Reader	no
VM	0%

Extensions (22)

Extension	Author (truncated)	Version
vs-keybindings	bot	0.2.11
githistory	don	0.6.20
gc-excelviewer	Gra	4.2.63
svg	joc	1.5.4
shaderlabformatter	lit	0.4.3
tmp-richtextsyntax	lmi	1.1.1
csdevkit	ms-	1.16.6
csharp	ms-	2.63.32
vscode-dotnet-runtime	ms-	2.2.8
debugpy	ms-	2025.4.1
python	ms-	2025.2.0
vscode-pylance	ms-	2025.3.2
remote-wsl	ms-	0.88.5
cpptools	ms-	1.23.6
powershell	ms-	2025.0.0
vs-keybindings	ms-	0.2.1
vscode-commons	red	0.0.6
vscode-xml	red	0.28.2025031108
se-csproj-extensions	sel	0.0.7
shader	sle	1.1.5
code-spell-checker	str	4.0.40
vstuc	vis	1.1.0

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31249601
vscod805:30301674
binariesv615:30325510
py29gd2263:31024239
14424t2-chatv6:31259161
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
iacca1:31171482
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
8did9651:31230678
hdaa2157:31222309
copilot_t_ci:31222730
f5992895:31254866
jda6j935:31233686
bgcontrol:31257677
fh1c7952:31258891
31787653:31256342

[vs-code-engineering]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.98.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[jamesford42]

Note, the reason I proposed just making the in-document search higher priority is because its actually a mode you can easily get out of, whereas the search panel youd have to intentionally clear the search box.