Quicklaunch: Mouse Hover Unintentionally Selects Search Results

[puffinjr]

Description

The "Quicklaunch" feature (activated by typing) automatically selects a search result if the mouse cursor happens to be hovering over it when results appear. This selection occurs without any explicit mouse movement, clicks, or keyboard navigation. Consequently, pressing "Enter" launches the inadvertently hovered item instead of the first result or a keyboard-selected one.

This behavior is problematic as the Quicklaunch modal's central display makes accidental hovering highly probable, leading to unintended launches and hindering efficient keyboard-driven workflows.

Screen.Recording.2025-06-11.203559.mp4

The first search result should be the default selection, or no result should be selected by default until the user explicitly interacts.
Moving the mouse cursor over a search result should highlight it visually, but not automatically select it. Selection should only occur via an explicit mouse click on a result or by using the ArrowUp or ArrowDown keys to navigate the results list.

This behavior significantly impacts usability for those who prefer keyboard-centric interaction or expect a predictable default selection. Any ideas to solve this?

homepage version

v1.3.2

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

I've attempted to mitigate this using custom JavaScript (e.g., trying to disable pointer-events on the results list), but have had no luck. Any assistance would be helpful.

[shamoon]

I suppose I don’t totally disagree but especially on the web this kinda stuff is rather non-trivial to control, especially without getting hack-y (read: error-prone), as it sounds like you have discovered with custom.js

Especially given the “solution” is to… move the mouse, I’m just not sure the juice is worth the squeeze on this one. But feel free, of course

[puffinjr]

I understand your perspective regarding the complexity. I guess I will have to begrudgingly accept this behavior or work on a client-side patch.