From e99ba63d922597a660786f45d481e985c6c71fac Mon Sep 17 00:00:00 2001 From: Atemu Date: Sat, 9 Aug 2025 15:57:38 +0200 Subject: [PATCH] views/UnifiedSearch: trigger on `f` input rather than qwerty keycode Before, search would trigger based on the physical keycode of the pressed key; whether that key would _represent_ f on a qwerty keyboard. Anyone not typing qwerty will have search trigger on the same physical button, regardless of whether that button actually types `f` in their respective layout. In my case, I use neo_qwerty which has a layer where the arrow keys are on ESDF. Attempting to jump forward word-wise using `C-` causes global search to open because `` is where f would be on qwerty. Any user with a keyboard layout other than qwerty should be affected by this bug. This makes it so that you have to press the `f` key of your particular layout; wherever that may be. Signed-off-by: Atemu --- core/src/views/UnifiedSearch.vue | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/views/UnifiedSearch.vue b/core/src/views/UnifiedSearch.vue index d7b2ca634ebaa..103e47b0425d3 100644 --- a/core/src/views/UnifiedSearch.vue +++ b/core/src/views/UnifiedSearch.vue @@ -129,7 +129,7 @@ export default defineComponent({ * @param event The keyboard event */ onKeyDown(event: KeyboardEvent) { - if (event.ctrlKey && event.code === 'KeyF') { + if (event.ctrlKey && event.key === 'f') { // only handle search if not already open - in this case the browser native search should be used if (!this.showLocalSearch && !this.showUnifiedSearch) { event.preventDefault()